For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 8 replies, 4 voices, and was last updated 19 years, 9 months ago by
.
-
Posts
-
Hi!
I am using OC4J standalone application server (10gas version 9.0.4) for development. Is it possible to debug jsp with this app server?
It seems that Eclipse does not find the generated source for the JSP.
What should I do to make it work?
Thanks a lot!
Support for JSR 45 spec and a 1.4 VM to run Eclipse and the app server is what is needed for successful JSP debugging. If 10g (Orion-based IIRC) supports JSR 45, you should be all set.
It’s absolutely fine although you have to use remote debugging. The best thing is, redeployment is faster than tomcat. Why?, because you do not have to restart the apps server, just change a time stamp on your OC4J server config files and off you go. I have to tweak though, hence I will share will the parameter that I use for remote debugging. Use this for your J2SDK default VM Arguments. It’s really detail, and tomcat miss out plenty of error codes. You also can add verbosity=5 in the Optional Program Arguments in MyEclipse-> Oracle9i/AS to make it even detail.
-Dhttp.session.debug=true -Ddatasource.verbose=true -Djdbc.connection.debug=true -server -Xdebug -Xrunjdwp:transport=dt_socket,address=40000,suspend=y
The only problem I had is, I can’t stop it properly using the application server stop button, I have to use a debugging stop button to stop the OC4J. Is MyEclipse can add redeploy button/option to OC4J by changing the timestamp on server configs files hence it will redeploy especially when we change the resource properties in our struts framework.
@putera79 wrote:
Use this for your J2SDK default VM Arguments. It’s really detail, and tomcat miss out plenty of error codes. You also can add verbosity=5 in the Optional Program Arguments in MyEclipse-> Oracle9i/AS to make it even detail.
-Dhttp.session.debug=true -Ddatasource.verbose=true -Djdbc.connection.debug=true -server -Xdebug -Xrunjdwp:transport=dt_socket,address=40000,suspend=y
I tried this command switch and it appeared to start the OC4J server without any problems. However, when I try to launch the remote debugger, I get the following message:
“Failed to connect to remote VM. Connection refused.”
Has anyone else had this error? How did you resolve it?
If you are launching OC4J from MyEclipse you don’t need to launch any remote debugger, the debugger is already connected, just start setting breakpoints.
@support-rkalla wrote:
If you are launching OC4J from MyEclipse you don’t need to launch any remote debugger, the debugger is already connected, just start setting breakpoints.
Unfortunately, when I reload the page, it does not stop at the specified breakpoints. There is no green tick next to the breakpoint icon to show that it connected.
Like the original poster, I am using OC4J standalone which I am told does not support the JSR-045 standard. As putera79 noted, I would need to debug this application remotely.
Have you tried this successfully? If so, how did you do it? Download OC4J 10g (9.0.4) standalone from:
http://www.oracle.com/technology/tech/java/oc4j/index.html
…and try debugging it with MyEclipse – it doesn’t work using MyEclipse’s internal debugger. If you do get it working, I would be most grateful if you can tell me how.
silver,
Have you tried following our remote debugging doc: http://myeclipseide.com/enterpriseworkbench/help/index.jsp?topic=/com.genuitec.myeclipse.doc/html/quickstarts/remotedebugging/index.htmlI would add that without JSR 45 support, debugging will be anywhere from flaky to unfunctional. Our debugger is based on the JSR 45 spec, so if the source maps we are getting back from the server aren’t what we expect there are issues that could popup.
