From the stack trace, it seems the problem was related to locating source
when a debug session started up. It should not have anything to do with
your setting SEP or refreshing it.
When did this error come up? During the setting of SEP, or when a debug
session started up because of the SEP? Are you using iSeries project by
any chance?
If you recompile a program, you need to use Refresh button to refresh the
SEP. Remove and re-add will not work.
One way to make sure the SEP server for you is cleaned up is click on the
triangle in the Service Entry Point view, and choose one of the "Clear
Service Entry Points" menu.
Thanks,
Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
"Aaron Bartell" <aaronbartell@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
16/10/2008 09:03 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc
Subject
[WDSCI-L] SEP Internal Error
Hi all,
I am getting an "Internal Error" dialog popping up each time I do a new
SEP
within WDSC. The error occurs when the SEP is processed the first time.
I cleared my .log eclipse file before I recreated the error and here is
what
the Java stack trace looks like:
http://code.midrange.com/b656a1db32.html
The bummer about this is that once the error happens and I recompile the
program, then a refresh of the SEP no longer works (i.e. in an attempt to
use it again). In fact I can't even remove and re-add it to get it
working
again. Instead I have to restart WDSC to get the SEP to work (ouch).
Unfortunately I do not know what I have done lately to my environment that
may have caused this.
Any ideas?
Aaron Bartell
http://mowyourlawn.com
midrange.com
