RE: jswat not breaking when running on tomcat 4.1.12

Just to be clear, the only software that changed was the Tomcat server,
right? Once the breakpoint is set, is it resolved? Run 'stop' then
'brkinfo X' to get the breakpoint information. If it is resolved, then I
suppose the only two possibilities are that the line of code in question
simply isn't running, or the JVM is broken. Okay, I suppose there's a
remote possibility that jswat is broken, but without reproducing it
myself I won't be able to make that determination.

Let me know. If I have time I'll try to reproduce it.

n


> -----Original Message-----
> From: William Lee [mailto:[email protected]] 
> Sent: Friday, October 04, 2002 2:26 PM
> To: [email protected]
> Subject: [jswat-user] jswat not breaking when running on tomcat 4.1.12
> 
> 
> I've recently upgraded to Tomcat 4.1.12 running on IBM SDK 
> 1.3 and jswat 
> 1.6 running on a Linux box.  I used to be able to have jswat running 
> perfectly on a Tomcat 4.0 environment.  It seems like, however, now 
> jswat does not seem to ignore all the breakpoints.  The Java command 
> line shoing in the ps looks like:
> 
> java -Xbootclasspath/p:/usr/java/lib/tools.jar -Xdebug 
> -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n 
> -Djava.endorsed.dirs=[path to some libs] 
> -Dcatalina.base=[tomcat home] 
> -Dcatalina.home=[tomcat home] -Djava.io.tmpdir=[tomcat home]/temp 
> org.apache.catalina.startup.Bootstrap start
> 
> Essentially, I'm using the catalina script to start tomcat, 
> so this is 
> the java command that the catalina script generates.
> 
> I then run jswat in the console mode and can attach to port 
> 8000 fine. 
> I can also set a breakpoint at a certain line all right, but 
> when I do 
> anything through the web browser, it doesn't seem to stop at 
> the break 
> point I set.  Does anyone have any clue on what can go wrong?