[Riyad Kalla]

AndyL,
If you are starting your app server with a custom app, then you need to connect the remote debugger to the running app server before you can debug. As of 3.8.3 full Java and JSP source lookup is available for remote debugging so you should be fine.

Instructions here: http://myeclipseide.com/enterpriseworkbench/help/index.jsp?topic=/com.genuitec.myeclipse.doc/html/quickstarts/remotedebugging/index.html

[andyl]

Hi Riyad, the problem is that the launcher is the “usual” Eclipse debug launcher, which starts Weblogic. Thus I cannot attach MyEclipse debug process to this launcher, because it is already in debug mode. So what I can do?

[Riyad Kalla]

andy, I asked our dev in charge of remote debugging and app servers and here is what he said:

Here’s the deal. To perform JSP debugging, you have to hook up the debug
process to our source locator, not the basic Eclipse one. This can happen
one of two ways: automatically by using our normal launching mechanism, or
by launching by another mechanism such that the external process will be
listening for debugger connections and then connecting our remote debugging
client to it (as in the Remote debugging tutorial). Since each external
application an support only one debugger connection, he simply cannot both
launch in such a way that Eclipse attaches its normal debug model while
simultaneously wanting to use ours. Something has to give.

Here’s what I’d suggest. Let him launch with his own model if he
likes, assuming it’s built on the Remote Java Application debugging
configuration. Once weblogic has spun up, go to the Debug View, right click
on the WebLogic process and select Disconnect from the context menu. Then,
have him go back to the launch configuration view and reconnect with our
‘Externally Launched Server’ connector as stated in the tutorial.

Naturally, I’ve never tested this, so his
milage may vary.

So it looks like you should either get rid of the custom launch method or do this manual step every time you want to debug.

[andyl]

Hi Riyad,
thanks for the help, but it still doesn’t work – the behavoir is the same: debugger stops in the jsp but is unable to find source…
I have started Bea with our launcher in “Run” mode and then connected to the running Bea with the remote MyEclipse launcher as you suggested – this works fine, I can debug Java code, also it works in general.
But for jsp’s there still “no source found”…
Which folder I should add in “Edit source lookup…” dialog? Is it the folder with jsp – sources or the folder with generated servlet *.java – files, or both? I have tried to add both folders but it seems do not change anything. Or I miss something?

[Riyad Kalla]

Very frustrating in deed… try and remove your deployment and rebuild your project, also make sure WebLogic is configured correctly:http://www.myeclipseide.com/FAQ+index-myfaq-yes-id_cat-18.html#97

and then recreate the deployment and retry.

[ranjan123]

weblogic 8.1 setup on myeclipse ide

[Author]

Posts