[william.l]

I’m trying to get debugging internally within MyEclipseIDE to work. I have a j2ee project with a jsp page. I set a breakpoint within the jsp. I deploy the app and start my Resin3 server and it will not stop at the breakpoint in my jsp page. Any clues?

I searched the forum and tried a number of things. From what I read it looks like users have debugging with Resin3 working, but I can’t see to get it to work. My application server is setup for Resin3 in debug mode. I’m also running Resin3.0.7.

I have also tried adding…
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
As optional Java VM Arguments in the Application Server/Preferences. I get the following error…

<A configuration error occurred during startup. Please verify the preference field with the prompt: Invalid listen port number:localhost:3119 Transport dt_socket failed to initialize, rc=-1.>

Does internally debugging not work with Resin, must I go the remote debugging route?

Thanks

*** Date: Tue Nov 22 14:29:30 CST 2005

*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.4.2_09

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 4.0.3 GA
Build id: 20051025-4.0.3-GA

*** Eclipse details:
Eclipse SDK

Version: 3.1.0
Build id: I20050627-1435

Eclipse Platform

Version: 3.1.0
Build id: I20050627-1435

Eclipse Java Development Tools

Version: 3.1.0
Build id: I20050627-1435

Eclipse Project SDK

Version: 3.1.0
Build id: I20050627-1435

Eclipse RCP

Version: 3.1.0
Build id: I20050627-1435

Eclipse Plug-in Development Environment

Version: 3.1.0
Build id: I20050627-1435

Eclipse Platform

Version: 3.1.0
Build id: I20050627-1435

Eclipse Java Development Tools

Version: 3.1.0
Build id: I20050627-1435

Eclipse Project SDK

Version: 3.1.0
Build id: I20050627-1435

Eclipse RCP

Version: 3.1.0
Build id: I20050627-1435

Eclipse Plug-in Development Environment

Version: 3.1.0
Build id: I20050627-1435

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\webenv\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
454_38
-vm
C:\WINDOWS\system32\javaw.exe

[Riyad Kalla]

Yes simply click and go debugging should work with Servlets/Classes no problem, but with JSPs some folks have reported problems. After looking into it, it does seems that Resin’s support for the JSR-45 debugging spec has some idiosynchrocies to it. Our connectors and debugger support the full JSR-45 spec, when an app server provides incomplete or trimmed down source maps to our debugger, it sometimes cannot decipher the appropriate locations in the code to break at. I did notice INtelliJ has this same problem, folks are unable to use the Generic JSR-45 app server debugging support with Resin and actually require a separate plugin just for that.

In the mean time for development we would suggest Tomcat or JBoss if you need an EJB container to get the best integration with IDEs (not just MyEclipse, but most IDEs seem to support these two pretty readily out of the box)

[william.l]

Should I also assume, that remote debugging with Resin3 will not work either. Tried that no luck either. I have not subscribed to MyEclipseIDE yet, I was evaluating the tool and the only show stopper was debugging jsp. Pretty much my options are to use a different container to debug jsp pages or wait for the folks at Resin to comply? Thanks for your help.

[Scott Anderson]

William,

Should I also assume, that remote debugging with Resin3 will not work either.

Remote debugging works just like debugging a local server launched through the custom Resin connector in MyEclipse.

Pretty much my options are to use a different container to debug jsp pages or wait for the folks at Resin to comply?

That about sums it up. We (or anyone else) can’t debug JSPs at the source level if the container doesn’t provide the necessary hooks. However, we make it really easy for you to keep synchronized deployments to any number of servers so what you might do is set up exploded deployments to both Tomcat 5 and Resin 3 and do your primary test / debug on Tomcat with quick checks on Resin for any sort of compatibility issues. That should allow you to keep your development really effective while still ensuring that Resin works as your production server. We’ve done similar stuff with JBoss / WebLogic / WebSphere for years.

[Author]

Posts