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 184371 - Deadlock when generating JUnit tests for Maven-based NBM project
Summary: Deadlock when generating JUnit tests for Maven-based NBM project
Status: RESOLVED DUPLICATE of bug 191796
Alias: None
Product: xml
Classification: Unclassified
Component: XAM (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Svata Dedic
URL:
Keywords: RANDOM, THREAD
Depends on:
Blocks:
 
Reported: 2010-04-16 15:23 UTC by Petr Jiricka
Modified: 2013-04-19 09:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (20.66 KB, text/plain)
2010-04-16 15:23 UTC, Petr Jiricka 		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 Jiricka 2010-04-16 15:23:45 UTC 
Created attachment 97546 [details]
Thread dump

I think I did the following:
1. Created a Maven-based NBM project
2. Created an Options panel through the wizard
3. Built the project
4. Generated JUnit tests for the options panel class
Comment 1 Petr Jiricka 2010-04-16 15:38:03 UTC 
The next time it passed -> RANDOM.
Comment 2 Jesse Glick 2010-04-16 16:06:47 UTC 
maven.model.Utilities.performPOMModelOperations acquires a lock on POMModelImpl while ProjectManager.mutex is held. XAM holds this lock while acquiring some semaphore: xam.AbstractModel.startTransaction. But it does not get this semaphore, and I am not sure what it is waiting for, so reassigning for evaluation.

Not a P2 if not known to reproducible or at least common, I think.
Comment 3 Sergey Lunegov 2010-04-19 08:21:03 UTC 
Nikita, please take a look.
Comment 4 Svata Dedic 2013-04-19 09:55:12 UTC 

*** This bug has been marked as a duplicate of bug 191796 ***