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 205315 - Deadlock when saving Maven project properties
Summary: Deadlock when saving Maven project properties
Status: CLOSED DUPLICATE of bug 204427
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF (show other bugs)
Version: 7.1
Hardware: PC Mac OS X
: P2 normal (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-19 17:16 UTC by Petr Jiricka
Modified: 2011-11-22 08:42 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (27.38 KB, text/plain)
2011-11-19 17:16 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 2011-11-19 17:16:38 UTC 
Created attachment 113337 [details]
Thread dump

Product Version: NetBeans IDE 7.1 RC1 (Build 201111171527)
Java: 1.6.0_29; Java HotSpot(TM) 64-Bit Server VM 20.4-b02-402
System: Mac OS X version 10.7.2 running on x86_64; MacRoman; en_US (nb)
User directory: /Users/petrjiricka/.netbeans/7.1rc1
Cache directory: /Users/petrjiricka/.netbeans/7.1rc1/var/cache

1. Created a Maven EE 6 EAR application
2. In the web module, opened project customizer, added JSF framework and PrimeFaces component suite
3. Clicked Ok -> Deadlock happened, see the attached thread dump
Comment 1 Petr Jiricka 2011-11-19 21:25:19 UTC 
Is this related to 204427? This happened to me again - does not seem to be random.
Comment 2 Martin Fousek 2011-11-21 06:33:18 UTC 
Right it's really similar to issue #204427. There is called reformat on created faces-config.xml file and it is stuck similarly to spring config files from #204427. Anyway not marking as a duplicate for now since I'm not sure how these deadlock will be resolved (if by fixing of any API, shared change in synchronisation which was done by mjanicek or fixing for every web framework itself - it's not advisable). I will update this issue once we will have solution for #204427.
Comment 3 Martin Fousek 2011-11-21 12:57:55 UTC 
Ok, since issue #204427 was resolved generally in the infrastructure, this issue will disappear with changeset web-main #f9f9e02059de. See bug #204427 for more details. It was the safest solution at this moment. Marking as duplicate since both issues are about the same troubles (when it doesn't require fixing for every framework itself).

*** This bug has been marked as a duplicate of bug 204427 ***
Comment 4 Marian Mirilovic 2011-11-21 16:06:51 UTC 
verified  duplicate