[James I. Falek]

Hi,

I am running TomCat 5 with JDK 1.3. I am able to deploy, redeploy and remove a web application. Sometimes, when I set a breakpoint, I get a round circle and sometimes it is a round circle with a check mark. TomCat stops (breaks) at the checkmarked breakpoints and ignores the non-checkmarked breakpoints. What is the difference between the two? I know that there must be some literature on this somewhere on the Eclipse site, but I can’t seem to find it.

More importantly, how do I move from unchecked to checkmarked? I have tried a rebuild and redeploy, but that doesn’t seem to affect it. I have tried to stop and restart TomCat as well as bring down Eclipse. Sometimes, I do get the checkmarked breakpoints, but it feels non-deterministic – which I know is not possible. Can someone steer me in the right direction?

As an aside, I have also seen this with WebLogic 7, but the behavior has been worse as the web application does not respond at all (at least with TomCat, it just ignores the breakpoints) and I have to restart everything and not use breakpoints at all. 😥

Thanks ahead of time

[Riyad Kalla]

GSX,
The check mark implies a class that has been loaded by the application server (which is why your breakpoints work). You need to be running Tomcat 5 with JDK 1.4 to get full support for the JSR 045 debugging spec that Tomcat implements… I’m actually surprised that debugging is working for you without it.

As Scott has mentioned in another thread… having Tomcat 5 is half the battle, you also need a JDK that supports the new debugging.

Please let us know if using 1.4 JDK helps.

[James I. Falek]

Hi,

The project is deploying to a JDK 1.3 enviornment and WebLogic 7. Prior to MyEclipse, I was able to use old genuitec plugins to set breakpoints with WebLogic 6 & 7 – so I am surprised that this is a JDK 1.3 / 1.4 issue.

I really want to use WebLogic, but I moved over to TomCat because the issue was even worse (see my previous post) using MyEclipse and WebLogic 7. I thought that if I can get some of this working with TomCat, then maybe some of the learnings could be applied to get WebLogic working. If not, then at least I could use the TomCat to debug the project.

So, focusing on TomCat, I changed the JDK in the preferences to JDK 1.4.2_03 and restarted the server and redeployed. I still have am getting the “unloaded” breakpoints (plain circles). Sigh. Any other suggestions?

Thanks again

[Riyad Kalla]

GSX, I appreciate your patience. I will ask Scott or Michael to weigh in on this for you.

[Scott Anderson]

Two things here. First, as Riyad said, the breakpoints will remain unchecked until the class is loaded. So, even if your application is running and you set a breakpoint in a JSP page, the breakpoint will remain unchecked until the class is referenced and loaded by the JVM.

Second, JDK 1.3 has a lot of problems related to remote debugging which is most likely causing the problems you’re seeing with WebLogic.

Overall, we really need more detail of *exactly* what you’re doing and what you’re expecting to have happen. For example, from your other posts I still don’t know if you’re setting your breakpoints in a java class or a JSP page. If you can provide the complete context around what you’re doing and expecting, as well as your environment configuration (see Posting Guidelines thread), we’ll be able to help further.

[James I. Falek]

Thank you for the help so far. Y’all have been wonderful and I think that I have the TomCat problem solved. I had inadvertantly reset the prefernces for automatic compile. Duh!

However, I still am having a problem with WebLogic – which is my real target platform and I am hoping that you can provide some insight into that problem.. I do a rebuild all projects and then deploy to weblogic. We are using WebLogic 7 with no service packs. I start weblogic through MyEclipse and after it finishes starting up, I add a breakpoint to a class. Sometime the breakpoint is checked while other times it is unchecked (even after fixing the automatic recompile). As you indicated, when it is uncheck, the breakpoint is never hit. In this case, the web application works fine, but just doesn’t hit the breakpoint.

However, when a breakpoint is check, the behavior of the system is either to work correctly (yea!) a minority of the time and break on the line or to essentially go to “outerspace” and provide no response. The web page that initiated the call looks like it is waiting for the response (in IE the world keeps on spinning and spinning), but there is no reaction from Eclipse. After this point, the web app is dead in the water – all subsequent requests follow the same pattern.

I have also tried to start weblogic outside of Eclipse, connect through the JDPA port and deply through MyEclipse. Eclipse seems to connect, but the behavior is the same as starting WebLogic from MyEclipse. I just pulled the old Genuitec plugins out last week, so I was thinking of reverting back to them (same configuration), but would rather try to get this working.

Thanks again,
James

– System Setup ——————————-
Operating System and version:
WindowsNT (sigh)
Eclipse version:
2.12
Eclipse build id:
200311030802
Fresh Eclipse install (y/n):
y
If not, was it upgraded to its current version using the update manager?
no
Other installed external plugins:
jad
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*:
7
MyEclipse version:
2.7 RC2
Eclipse JDK version:
JDK 1.31_08
Application Server JDK version:
JDK 1.31_08
Are there any exceptions in the Eclipse log file?
yes ❗
!SESSION Feb 18, 2004 13:41:03.289 ———————————————
java.version=1.3.1_08
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/ibiIDE/eclipse/
!ENTRY org.eclipse.core.resources 2 1 Feb 18, 2004 13:41:03.289
!MESSAGE Skipping builder net.sourceforge.metrics.builder for project workbench. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.

[Riyad Kalla]

GSX,
Before we jump ship can you do an upgrade to at least JDK 1.4.1 and try debugging again? I know you mentioned that your deployment environment is 1.3, but if you need debugging then you really need a app server that supports JSR-45 (which IIRC Weblogic 7 does) in that case you need to be using the 1.4 JDK to really get the correct debugging experience.

Also when you upgrade, don’t forget to adjust the Installed JREs in Window>Prefs>Java>Installed JREs and also change the JDK used to launch Weblogic

I really want to avoid troubleshooting and tearing our hair out all day when the only solution is to upgrade. Hopefully developing with 1.4 for debugging will still allow you to deploy properly on 1.3

[James I. Falek]

Hi,

After reading many, many posts in the support forum, I just tried your recommendation and I am “cautiously optimistic”. I am now starting Eclipse with JDK 1.4.2 and am starting WebLogic 7 with JDK 1.4.2 while still compiling the code against JDK 1.3 . It looks good and I am very pleased! 😀 Thank you!

One more question, if you don’t mind. You suggested updating the Window>Prefs>Java>Installed JREs to include the JDK1.4. I haven’t done that but just added JDK 1.4 to MyEclipse WebLogic JDK . Adding it to MyEclipse in this fashion did not add it to Eclipse. So, it is not in the Eclipse JDKs, but it is in the MyEclipse WebLogic JDKs. Is there any reason to add it to the Eclipse list of JDKs?

Again, thank you for all of the give and take. It is a great product and I look forward to using it for a long time to come! 😀

[Riyad Kalla]

Is there any reason to add it to the Eclipse list of JDKs?

No I suppose not; I haven’t ever added a JDK this way because I usually only deal with 1 installed on my machine at a time. If this is working for you then that sounds great.

Again, thank you for all of the give and take.

No problem, thanks for being so cooperative during the troubleshooting. Sometimes the user wants us to wave a magic wand and fix things, which is hard since we weren’t given wands with the job 😀

[Scott Anderson]

I haven’t done that but just added JDK 1.4 to MyEclipse WebLogic JDK . Adding it to MyEclipse in this fashion did not add it to Eclipse. So, it is not in the Eclipse JDKs, but it is in the MyEclipse WebLogic JDKs. Is there any reason to add it to the Eclipse list of JDKs?

Actually, adding it using the MyEclipse JDK add button is just a shortcut to adding it to your installed JRE’s. Once you hit OK, you should see that JDK listed in your Window > Java > Installed JREs list the next time you open the config dialog.

Sometimes the user wants us to wave a magic wand and fix things, which is hard since we weren’t given wands with the job.

I was given a wand. Wayne gave it to me personally. Damn thing’s busted though. No wonder he was so eager to part with it. 😉

[Author]

Posts