- This topic has 6 replies, 3 voices, and was last updated 17 years, 11 months ago by lpcnucci.
-
AuthorPosts
-
sri_bitlaMemberHi,
I am trying to debug a remote weblogic server. The weblogic server is running on linux box and I have configured the server to start in debug mode.
I have created a new “MyEclipse Externally Launched Server” to connect to the remote weblogic server. It successfully connected and I see all that thread information in the debug view. But when I sent a request to the weblogic server the Java source code is not opening in the MyEclipse editor for debugging. I am sure that the request will hit the breakpoint. The request is processed as if the server was running in run mode and not in debug mode. Everything seems to be fine with no error messages but dont understand why the source code is not opening in the editor for debugging.
I have only Java source code and no JSP files. I used Ant to build and deploy my application.
Here is my configuration
MyEclipse 4.0
Eclipse 3.1
Weblogic 9.0 on linux
jrockit90_150_03Thanks,
Srinivas.
Riyad KallaMemberSrinivas,
If you try and upgrade to Eclipse 3.1.2 and MyEclipse 4.1.1 can you successfully debug? It’s possible that this was a bug that was corrected in either the Eclipse debugger of MyEclipse.
sri_bitlaMemberHi Riyad,
Thanks for the reply. I have done what you said but there was no luck and no difference in the outcome. I upgraded Eclipse to 3.1.2 and MyEclipse to 4.1.1.
Any clue about what could be the problem?
Thanks,
Srinivas.
Riyad KallaMemberAhh, I missed this detail:
I used Ant to build and deploy my application.
Make sure your javac target has debug=”true” set so the class files include the debugging information.
sri_bitlaMemberHi Riyad,
Thanks for the reply. I have found the problem. The problem is that I have weblogic with an Admin Server and a Managed Server with my application deployed to the Managed Server. The Admin Server started in debug mode while Managed Server has not.
Weblogic starts Admin Server and Managed Server in their own JVMs and the debug options (like -Xdebug portnumber etc…) that were set in setDomainEnv.sh were applied to Admin Server only. So weblogic starts Admin Server in debug mode and Managed Server in run mode. Because until now I was deploying the application to Managed Server, which is not running in debug mode, I couldn’t get the debugging to work. Now I moved the deployment of my application from Managed Server to Admin Server and I could debug the code.
Thanks,
Srinivas.
Riyad KallaMemberAhh glad to hear it, and thank you for following up so others may learn from this thread.
lpcnucciMemberSorry to dredge up an old topic, but I’m having the same problem and don’t have the option to move the application from the managed server to the admin server. Any tips on how to get the managed server to start in debug mode?
-
AuthorPosts