[Narayan Iyer]

All,

Here;s the scenario:

I use MyEclipse to connect to Resin pro 3-1-3 (Remote Debugging). I did the following:

1. Check-out source code from CVS
2. Created a new Java-Project in MyEclipse.
3. From Preference-Java Build Path added Libraries (Resin & App Jars) in Libraries Tab
4. In Source Tab, I link all the folders from the project to checked-out source files

However, when I tried to setup remote debugging, here’s my finding:

1. I cant run resin (httpd.exe (windows) or httpd.sh (mac)) within myeclipse using resin 3.x connector in remote debug mode. It does come up … however for some reason it is not picking up the following entry in resin.conf:

<jvm-arg>-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9999</jvm-arg>

However, if I just use the command-prompt (both win & mac) it works!!! Here’s a sample
output:

Jun 16, 2008 8:40:35 PM com.caucho.boot.WatchdogProcess run
INFO: WatchdogProcess[Watchdog[],1] starting Resin
[20:40:35.243] {watchdog-} WatchdogProcess[Watchdog[],1] starting Resin
Listening for transport dt_socket at address: 9999

The above socket address 9999 is missing when resin is configured to start/stop within MyEclipse!

2. To create a remote profile, there are 2 ways of doing: (First start resin server from command line)

1. Create new debug profile (Open Debug Dialog) and then create a new profile under Remote Java Application (provide all socket details). Then click debug. It connects … however it is not obvious straight-away … it is obvious only if we open the debug perspective! After this it is clear that the debugger is indeed attached to the configured port 9999.

2. As suggested in MyEclipse tutorials, Open Debug Dialog and choose MyEclipse Externally Launched Server and follow the same steps as above. However, this does not work!!!!

3. Even if I set it up to work (command-line & remote java application), I am still unable to debug (step through) jsp breakpoints!!! Why?

So summarizing , here are my pain points:

1. Unable to Run/Start/Resin server from inside MyEclipse in remote debugging mode.
2. Unable to configure MyEclipse Externally Launched Server for debug as claimed in tutorials.
3. Unable to step through JSP pages. Its as though, it is not recognizing these breakpoints, although I could see it defined in the breakpoints tab in Debug perspective.
4. How do I configure the Debug Dialog Profile with the Debug perspective?

Honestly, I could get the whole application running using the Eclipse Classic!!! So I just ended up buying the professional license and obviously it is of no use to me!!!

Hope you prove me wrong!!! If not can I have a refund???

Thanks
-Narayan Iyer-

[Riyad Kalla]

Narayan,
Let me clarify a few things first:

* The MyEclipse application server connectors are only intended to run locally installed servers.
* The connectors, when run in Debug mode, automatically set *all* those arguments for you AND connect the debugger to the running server process. You don’t need to set anything.
* Remote Debugging in MyEclipse is only intended to connect to remote servers that are running the server you want to debug (not on the same machine).

And yes absolutely, if MyEclipse is not helpful to you, you can have a full refund any time. Just email us and let us know (subscriptions@genuitec.com)
* When debugging, your project needs to be a web project with a properly configured Source and WebRoot directory so the Class and JSP references can correctly be resolved inside the project paths.
* JSP debugging with Resin has been flaky in the past, it’s possible it is still. I’ve filed a bug for our dev team to look into the issue for the 7.0 release.

[Author]

Posts