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.
Build: NetBeans IDE Dev (Build 100707-075a8617b9bc) VM: Java HotSpot(TM) Client VM, 16.3-b01, Java(TM) SE Runtime Environment, 1.6.0_20-b02 OS: Linux User Comments: alexeybutenko: Add JSF framework to the Maven Web App alexeybutenko: Happens after http://statistics.netbeans.org/analytics/detail.do?id=171168 and it is unable to open project properties after that Stacktrace: java.lang.IllegalStateException: Current thread has already started a transaction at org.netbeans.modules.xml.xam.AbstractModel.startTransaction(AbstractModel.java:392) at org.netbeans.modules.xml.xam.AbstractModel.startTransaction(AbstractModel.java:380) at org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:170) at org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:141) at org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:136) at org.netbeans.modules.project.ui.actions.CustomizeProject.actionPerformed(CustomizeProject.java:150)
Created attachment 100641 [details] stacktrace
Reassigned to maven
This bug already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=171223
No report in the list of exceptions from 6.9. Changing to "dev". Most probably always caused directly by issue 188363 and might be closed as duplicate. The only question here is if maven code could be made more robust if a project creation fails (as in the case of issue 188363), so that a XAM transaction does not stay started.
Created attachment 100791 [details] stacktrace
I think it's the same. Happened to me, but likely because I run w/o enterprise cluster so the hotfix did not apply. *** This bug has been marked as a duplicate of bug 188363 ***