Re: jswat not stopping at breakpoints

It doesn't sound like you're doing anything wrong, in fact that's just 
the sort of use-case I had imagined. A few things to look for are:

1. Are there any errors or warnings in the Output window (in the 
"Debugger Console" tab) regarding breakpoint resolution?

2. Open the Breakpoints window (open via Breakpoints or Window menu), 
click on the breakpoint that is not working, and look at its properties 
in the Properties window (open via the Window menu).

  a. Is the disabled checkbox next to 'Resolved' checked or not?

  b. Likewise, the breakpoint should be Enabled, and have a Skip Count 
of zero.

  c. The Suspend Policy should be either "All threads" or "Event thread" 
in order for the breakpoint to stop.

  d. Is there a Thread Filter set? 'null' is the default value, which 
means there is no thread filter.

3. Was your web app compiled with the -g flag to enable line number 
information?

If all of these conditions are okay, then this sounds like a bug, in 
which case I'll try to reproduce it. Were you using Windows or a Unix 
variant? Which version of Tomcat are you using?

Can you try using version 3.7, just in case the problem went away by itself?

n


Brian Moseley wrote:
> i've used previous versions of jswat 3.x to debug webapps running in
> tomcat with much success, but after upgrading to 3.6 some time ago,
> i'm experiencing an odd phenomenon - my breakpoints are being ignored.
> 
> here's what i did:
> 
> 1) in a new session, added a few directories to the source path
> 2) started tomcat (5.5.9) with 'jpda start'
> 3) attached the session
> 4) opened a source file by finding a class in the classloader for my
> webapp in the Classes panel
> 4) set a breakpoint on a line of code in the source file
> 5) made an http request to tomcat
> 
> jswat never stopped at my breakpoint but sailed right past it.
> 
> i'm sure i'm doing something silly, but i can't figure out what it
> might be. have i overlooked something obvious? thanks!