| Summary: | Tomcat threads are suspended while running in debug mode | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Gary Karasiuk <karasiuk> | ||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||
| Status: | CLOSED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | Michael_Rennie | ||||
| Version: | 3.6.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Gary Karasiuk
Created attachment 196975 [details]
screenshot that shows suspended thread
Can you confirm there are no breakpoints set (using the breakpoints view)? From the screenshot it says you are suspended on a RuntimeException, so you probably have an exception breakpoint set. (In reply to comment #2) > Can you confirm there are no breakpoints set (using the breakpoints view)? From > the screenshot it says you are suspended on a RuntimeException, so you probably > have an exception breakpoint set. There are no Exception breakpoints set. I should add that I am hitting this suspension, as part of the thread dying. I think that Tomcat triggers a runtime exception, to effectively kill the thread. If I start single stepping the thread I end up in an uncaught exception handler. (In reply to comment #3) I should also add that this happens on both the SUN and the IBM JVMs. (In reply to comment #3) > There are no Exception breakpoints set. How about option on the Java > Debug preference page -> Suspend execution on uncaught exceptions, it it enabled? Ah, I didn't see the Java > Debug preference page instead I was looking on the Run/Debug set of pages :-( Thanks for pointing that out. Closing as invalid ... although it would great if someone could think of a way to make this more user friendly. |