[mhartnett]

I have read a number of other posts here and have tried to resolve this problem but nothing has worked. I was wondering if anyone has solved this issue. I have read a lot about upgrading to JDK 1.4.1_03 but the application we are working on is using 1.3.1 and upgrading would not be an option.

I am having a problem debugging using Eclipse 2.1 and MyEclipse 2.6.1.
If I start the server and run the application everything works fine.

If I put a breakpoint into my code and then run the application I do not see the application breaking at all. I am in debug perspective of Eclipse. The browser just hangs and will not respond. I can take the breakpoint off and refresh the browser and it works fine again.

Do I need to have anything special in a configuration file for weblogic to enable debugging ?

Do I need to start the JVM with any special options. I am currently using the following startup options. I have tried a number of configurations on the startup options and nothing works.

-hotspot -ms64m -mx256m -Xdebug -Djava.compiler=none -Xnoagent -Dweblogic.ProductionModeEnabled=false

Do I need to add anything to my classpath ?

I am using Weblogic 6.1 and JDK 1.3.1_09 and I created the project as a Web project. I am setting a break point in a java class that is called from a JSP.

Thanks in advance for any help…

[support-michael]

Check your Weblogic6 Launch preference and confirm that “Start Weblogic” launches in Debug mode
Window->Preferences->MyEclipse->Application Server-> Weblogic6->Launch.

Michael
MyEclipse Support

[Scott Anderson]

Also, I’d drop the -hotspot and -Dweblogic.ProductionModeEnabled optoins as these are taken care of by the connector.

–Scott
MyEclipse Support

[mhartnett]

Hi Scott,

I have tried both of those options and do not have hotspot and ProductionModeEnabled as part of my JVM options. I am starting Weblogic in debug mode. My environment is Win2000.

I still get the same results. The application that I am testing with is the simple helloworld provided by your tutorial.

I did a basic install of Weblogic 6.1 sp2. I also read another post that suggested adding a number of directroies to the class path. I have tried that as well but still with the same results. .. here is the link: https://www.genuitec.com/forums/topic/breakpoint-problem-closed-2/&highlight=weblogic

Additionally, when this happens and I stop and restart my server, the ports are not released and the server shuts down automatically. Perhaps this is a problem that cannot be resolved. I does not seem that anyone has found a resolution yet.

On the upside, MyEclipse is definately a well needed set of plugins for this IDE.

By the way – here is the output after the request is made when debug is on:

<Sep 5, 2003 9:17:26 AM EDT> <Info> <NT Performance Pack> <Allocating: ‘2’ NT reader threads>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: init>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: param verbose initialized to: true>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: param packagePrefix initialized to: jsp_servlet>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: param compilerclass initialized to: javac>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: param srcCompiler initialized to weblogic.jspc>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: param superclass initialized to null>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: param workingDir initialized to: C:\bea\wlserver6.1\config\mydomain\applications\HelloWorld\WEB-INF\_tmp_war_myserver_myserver_HelloWorld>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: param pageCheckSeconds initialized to: 1>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: initialization complete>
<Sep 5, 2003 9:17:26 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] *.jsp: pageCheckSeconds over-ruled in JSPServlet to : 1>
<Sep 5, 2003 9:17:27 AM EDT> <Info> <HTTP> <[WebAppServletContext(114314,HelloWorld,/HelloWorld)] Generated java file: C:\bea\wlserver6.1\config\mydomain\applications\HelloWorld\WEB-INF\_tmp_war_myserver_myserver_HelloWorld\jsp_servlet\__helloworld.java>
<Sep 5, 2003 9:19:32 AM EDT> <Info> <Management> <Configuration changes for domain saved to the repository.>

Thanks for your help.

[Scott Anderson]

I’ll look into this deeper and see if I can replicate the behavior with JDK 1.3.1 and find a workaround.

–Scott
MyEclipse Support

[Scott Anderson]

Well, I tried to replicate this behavior but could not. I’m using Windows 2000, Eclipse 2.1.1, MyEclipse 2.6.1 and I launched WebLogic with JDK build 1.3.1-b24. One difference might be that I’m launching Eclipse itself with JDK 1.4.1. Or, possibly your environment path has an even earlier JDK on it somewhere (Windows System directory) that is causing trouble. The problem seems environmental, but may be tough to run down. How long ago did you install your JDK? A reinstallation of it might be something to try too. I wish I could be more specific, but unfortunately that’s about all I know at present.

–Scott
MyEclipse Support

[Author]

Posts