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 188437 - IllegalStateException: Current thread has already started a transaction
Summary: IllegalStateException: Current thread has already started a transaction
Status: RESOLVED DUPLICATE of bug 188363
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.0
Hardware: All All
: P2 normal (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on: 188363
Blocks:
  Show dependency tree
 
Reported: 2010-07-07 10:14 UTC by Alexey Butenko
Modified: 2010-07-13 14:00 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 171223


Attachments
stacktrace (2.83 KB, text/plain)
2010-07-07 10:14 UTC, Alexey Butenko
Details
stacktrace (2.91 KB, text/plain)
2010-07-13 01:51 UTC, Jesse Glick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Butenko 2010-07-07 10:14:10 UTC
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)
Comment 1 Alexey Butenko 2010-07-07 10:14:14 UTC
Created attachment 100641 [details]
stacktrace
Comment 2 Sergey Lunegov 2010-07-07 10:17:51 UTC
Reassigned to maven
Comment 3 Exceptions Reporter 2010-07-08 13:02:42 UTC
This bug already has 5 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=171223
Comment 4 Antonin Nebuzelsky 2010-07-09 12:27:49 UTC
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.
Comment 5 Jesse Glick 2010-07-13 01:51:21 UTC
Created attachment 100791 [details]
stacktrace
Comment 6 Jesse Glick 2010-07-13 14:00:15 UTC
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 ***