Radhakrishnan J wrote:
Eclipse's Debug UI shows the breakpoints threadwise. If these executions
are happening over different threads, thats one way to tell the difference.
It's not the thread that's the issue - it's which _webapp_ it's
currently executing. That's what the OP cared about - to stop in a
particular class if it was being executed out of webapp1, but not in
webapp2.
The thread pool of HTTP connectors is shared by all webapps in a Tomcat
instance, so merely knowing "which thread" hit the breakpoint is
useless, unless you can also convey in some form what webapp it is
currently executing the code for.
This information is not easily (perhaps not at all - I'm not an expert)
available in the current JVMTI API (and definitely not in the JVMDI
API), so the debugging agent won't be able to tell which webapp the code
is executing at the moment.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
