- This topic has 4 replies, 2 voices, and was last updated 21 years, 5 months ago by
.
-
Posts
-
I’m trying to figure out how to debug an application (web and ejb) using MyEclipse and WebLogic 7.0. I’m used to WSAD and WebSphere but now find myself in a WebLogic environment. So I just download Eclipse and MyEclipse. I can get WebLogic started from Eclipse and deploy my application. However, when I set a breakpoint in my servlet (for example) and then launch a browser and link to that page, the browser waits as if waiting for me to take action in the debugger – but the debugger does not allow me to step through the code. Does anyone have a step by step procedure and/or examples on this? 🙁 🙁
I did a quick search for ‘Weblogic hangs’ in the forums and found this thread where we’ve run this issue down before. I believe it will provide the information you need:
https://www.genuitec.com/forums/topic/weblogic-7-0-hanging-up-with-jsp-debugging-closed/&highlight=weblogic+hangs–Scott
MyEclipse Support@scott wrote:
I did a quick search for ‘Weblogic hangs’ in the forums and found this thread where we’ve run this issue down before. I believe it will provide the information you need:
https://www.genuitec.com/forums/topic/weblogic-7-0-hanging-up-with-jsp-debugging-closed/&highlight=weblogic+hangs–Scott
MyEclipse SupportI read that discussion earlier and agree that that is probably the core problem. I set my path so that the OS found the JRE in WebLogic first (jdk131_06), set the Eclipse default JRE to the same, and set WebLogic JRE in MyEclispe to that JRE also. With those setting I do get a very extensive list of running threads for WebLogic (more than I see with any other combinations of JREs).
Prior to starting WebLogic from Eclipse, I can step through a simple Java application (not one deployed to WebLogic). Once I start/stop WebLogic, I can no longer step through the same Java application (unless I restart Eclipse). Other combinations of JREs and using the -vm option on Eclipse startup, either allow no debugging or a result similar to the above.
I am not currently setting any JAVA_OPTIONS on WebLogic startup (e.g. for debugging). Do I need something here? Also, confusing, I am debugging a remote VM or local when using MyEclipse? Do I suspend a thread or not?
You’ll have the best results for debugging using JDK 1.4.1 or 1.4.2 since the debugger will then allow hotswap debugging to work. The older JDK 1.3.1 builds have been problematic in some instances as you’ve seen.
I am not currently setting any JAVA_OPTIONS on WebLogic startup (e.g. for debugging). Do I need something here?
No you don’t. WebLogic is started in debug mode when launched by MyEclipse.
Also, confusing, I am debugging a remote VM or local when using MyEclipse?
You’re debugging a remote VM as if it was local. That’s why we suggest using JDK 1.4.1/2 since the remote debugging support is so much better than 1.3.1.
Do I suspend a thread or not?
When you’re stopped at a breakpoint within WebLogic, the Eclipse debugger should show a suspended WebLogic thread and the full stack of that thread in the Debug View.
–Scott
MyEclipse Support@scott wrote:
You’ll have the best results for debugging using JDK 1.4.1 or 1.4.2 since the debugger will then allow hotswap debugging to work. The older JDK 1.3.1 builds have been problematic in some instances as you’ve seen.
I am not currently setting any JAVA_OPTIONS on WebLogic startup (e.g. for debugging). Do I need something here?
No you don’t. WebLogic is started in debug mode when launched by MyEclipse.
Also, confusing, I am debugging a remote VM or local when using MyEclipse?
You’re debugging a remote VM as if it was local. That’s why we suggest using JDK 1.4.1/2 since the remote debugging support is so much better than 1.3.1.
Do I suspend a thread or not?
When you’re stopped at a breakpoint within WebLogic, the Eclipse debugger should show a suspended WebLogic thread and the full stack of that thread in the Debug View.
–Scott
MyEclipse SupportI switched to JDK 1.4.2 and everything is working. Thanks!!! The check is in the mail.
