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 80783 - Deadlock during project classpath scanning
Summary: Deadlock during project classpath scanning
Status: VERIFIED DUPLICATE of bug 74362
Alias: None
Product: xml
Classification: Unclassified
Component: XML Multiview (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-21 08:41 UTC by Petr Blaha
Modified: 2007-09-25 01:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread dump (14.80 KB, application/octet-stream)
2006-07-21 08:42 UTC, Petr Blaha 		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 Petr Blaha 2006-07-21 08:41:38 UTC 
[NB 5.5 Beta2, jdk 1.6.0]
I created new Web Project with Jboss target server, then switched the project
for Glassfish. During project classpath was deadlock. Thread dump is attached.
Comment 1 Petr Blaha 2006-07-21 08:42:39 UTC 
Created attachment 32078 [details]
thread dump
Comment 2 Radko Najman 2006-07-21 09:25:47 UTC 
From the attached thread dump it seems like a XmlMultiViewEditorSupport issue.
Reassigning.
Comment 3 Milan Kuchtiak 2006-07-21 09:51:54 UTC 
Seems that deadlock occurs when web.xml is being open in editor.
Does that happen also when switching from Tomcat to GlassFish ?
This doesn't seem to be related to project classpath scanning.

Reassigning to Erno.
Comment 4 Erno Mononen 2006-07-21 09:55:58 UTC 
Which build of JDK 1.6 are you using?
Comment 5 Petr Blaha 2006-07-21 09:57:44 UTC 
[blaha@localhost bin]$ ./java -version
java version "1.6.0-rc"
Java(TM) SE Runtime Environment (build 1.6.0-rc-b91)
Java HotSpot(TM) Client VM (build 1.6.0-rc-b91, mixed mode, sharing)
Comment 6 Erno Mononen 2006-07-21 09:59:13 UTC 
Stupid question, I can see it from the attached thread dump. Please try with a 
later build, looks like a duplicate of issue 74362.
Comment 7 Petr Blaha 2006-07-21 10:12:20 UTC 
I'm sorry, I was able to reproduce the bug with jdk 1.6.0 b.79, b.82 but not in
b.91. It seems as fixed in latest jdk 1.6.0 builds.
Comment 8 Erno Mononen 2006-07-21 10:12:48 UTC 
Closing as a duplicate, it is a JDK 1.6 issue and fixed builds later than b83.

*** This issue has been marked as a duplicate of 74362 ***
Comment 9 Mikhail Matveev 2007-09-20 12:52:12 UTC 
Verified duplicate