- This topic has 10 replies, 4 voices, and was last updated 20 years, 4 months ago by
.
-
Posts
-
Using your application server documentation, I was able to launch and debug an application on a Weblogic 8.1 server using Eclipse. However, I had to specify the Weblogic installation directory in the connector configuration. Doesn’t this imply that the connector can only be used for a Weblogic server that is installed locally?
Can you provide a procedure to connect to a remote QA Weblogic server that is running as a service? Is this possible at all?
Thank you
Here is a link to another thread dealing with Tomcat, but the steps are similar: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-2585-highlight-remote+debugging.html
Once you have your app server setup correct for remote debugging, you can easily setup the Eclipse debugger to connect.
I read those articles and made the following changes to my configurations: I added the following parameters to the JAVA_OPTIONS variable in my startWebLogic.cmd file.
-Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=3999,suspend=n -Xdebug -Xnoagent
Also, I am using a weblogic.xml file with the following jsp-param:
<param-name>debug</param-name>
<param-value>true</param-value>I start a debug perspective in Eclipse and connect to port 3999. Now I can deploy a project and debug Servlets. However, I can’t get JSP debugging to work!. Any ideas?
To get JSP debugging to work you need to be using a JSR 45 complient server and JDK 1.4 on the server and for running Eclipse. We suggest a late release of 1.4.1 or the most recent 1.4.2_05 JDK to get good debugging support.
Also check out Scott’s reply here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-84-highlight-weblogic+debug.html, there are some issues with WebLogic’s default server settings to compile JSP pages for production, not for debugging.
I believe my problem is that I am not configuring Weblogic properly for JSP debugging. When I launch my local Weblogic server with Eclipse (my local Weblogic server is identical to the remote server and both are launched with the JDK provide by BEA), I am able to debug the JSP page in my project. The only difference I can see is the way Weblogic is being started up. What settings does the myeclipse connector use to launch Weblogic?
Thank you.
I believe my problem is that I am not configuring Weblogic properly for JSP debugging
Most likely you are right, did you use the link above to configure your remote app server to compile the JSP files with debugging? Also make sure your remote server is running with JDK 1.4+ like I mentioned above.
What settings does the myeclipse connector use to launch Weblogic?
I will ask.
The problem with debugging JSP’s on a remote server is that the source lookup is handled by our JSP source locator and that is put “in the loop” by the connector launch. As a result, source level JSP debugging when you’ve launched the server manually and remotely simply isn’t possible since our source locator isn’t specified as part of the launch and Eclipse will use the default.
@support-scott wrote:
As a result, source level JSP debugging when you’ve launched the server manually and remotely simply isn’t possible since our source locator isn’t specified as part of the launch and Eclipse will use the default.
taglibs are other precompiled classes are fine though ?
forgive my ignorance if this question is obvious, but is there a ‘myeclipse way’ of starting an appserver remotely ?
taglibs are other precompiled classes are fine though ?
Yes, those should be fine as they’re straight Java code so the built-in Java source locator can find them.
forgive my ignorance if this question is obvious, but is there a ‘myeclipse way’ of starting an appserver remotely ?
Actually, that’s a good question. Unfortunately, the answer is currently “no” because the source locator used is tied to the launch type. Since you’re trying to use the “Remote Java Application” to hook up and debug the remotely launched server it will use the default Java-only source locator. However, I don’t see why we couldn’t provide a launch configuration type that provides the correct source locator that could be used for remote debugging. I’ll file an enhancement request for it, but don’t expect it by 3.8GA. 3.9, it’s got a real shot though. 🙂
@support-scott wrote:
However, I don’t see why we couldn’t provide a launch configuration type that provides the correct source locator that could be used for remote debugging. I’ll file an enhancement request for it, but don’t expect it by 3.8GA. 3.9, it’s got a real shot though. 🙂
sweet ! As an aside, when running an application with debugging enabled there is a performance penalty right ? It would be *amazing* to run a production with debugging enabled (barring any security issues) and be able to attach a debugger to it to catch those hard to reproduce bugs…
note: I think you should turn this thread into a document to be referred to..
As an aside, when running an application with debugging enabled there is a performance penalty right ?
That is always the case with any kind of debugging in any language. 🙂
note: I think you should turn this thread into a document to be referred to..
Well, I made the post ‘Sticky’ so it will hang around the top of the forum so others can find it easier. That’ll have to do for now.
