This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 97334 - hang on exit if stopped at BP
Summary: hang on exit if stopped at BP
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-07 01:22 UTC by Vince Kraemer
Modified: 2007-03-15 10:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
the thread dump (27.43 KB, text/plain)
2007-03-07 20:21 UTC, Vince Kraemer 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vince Kraemer 2007-03-07 01:22:27 UTC 
to reproduce

start nb
add a gf domain
create a web app targeted at the domain
set a bp in the index.jsp
debug the project
wait for the ide to hit the BP
File->exit

you are hung
Comment 1 Jiri Skrivanek 2007-03-07 08:11:32 UTC 
What is the thread dump? Isn't it related to issue 97082?
Comment 2 Vince Kraemer 2007-03-07 16:34:03 UTC 
No this issue is not related to issue 97802... I just stumbled on it when I was
working on 97802, though...

In this case, the debug info is removed from the debug info map, BEFORE the map
is used to test if the server is stopped at a BP...

The fix is easy, but needs to get called out as a different issue.

I don't want to mix multiple bugs into the check in for one specific issue,
since a revert may undo both...
Comment 3 Vince Kraemer 2007-03-07 20:21:51 UTC 
Created attachment 39267 [details]
the thread dump
Comment 5 Nitya Doraisamy 2007-03-07 23:41:28 UTC 
Verified fix in latest 6.0 build 20070307-2210
Comment 6 _ pcw 2007-03-08 08:16:31 UTC 
Reviewed, looks good.  Verified in 5.5.1 branch.
Comment 7 Jiri Skrivanek 2007-03-08 11:26:14 UTC 
I tested it in NB6.0 20070308-0631 and it seems to be fixed. I would leave this
issue opened until it is fixed in release551 branch.
Comment 9 Michal Mocnak 2007-03-15 10:33:56 UTC 
Verified