Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356215 - Opening a freshly imported project using "unknown" reused projects for the first time results in unexpected error
Summary: Opening a freshly imported project using "unknown" reused projects for the fi...
Status: CLOSED DUPLICATE of bug 354399
Alias: None
Product: Jubula
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: All Linux
: P3 minor (vote)
Target Milestone: Indigo SR1   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-30 11:18 EDT by Oliver Goetz CLA
Modified: 2011-09-15 06:10 EDT (History)
1 user (show)

See Also:

Attachments
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 Oliver Goetz CLA 2011-08-30 11:18:20 EDT 
After importing a project that uses "unknown" reused project the attempt to open this project ("Open project immediately after import" checked in import dialog) results in an UE:


3004: Unexpected error occurred.
  java.util.ConcurrentModificationException
  	at java.util.IdentityHashMap$IdentityHashMapIterator.nextIndex(Unknown Source)
  	at java.util.IdentityHashMap$KeyIterator.next(Unknown Source)
  	at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.calculateChanges(UnitOfWorkImpl.java:605)
  	at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.writeChanges(RepeatableWriteUnitOfWork.java:414)
  	at org.eclipse.persistence.internal.jpa.EntityManagerImpl.flush(EntityManagerImpl.java:744)
  	at org.eclipse.persistence.internal.jpa.EJBQueryImpl.performPreQueryFlush(EJBQueryImpl.java:1269)
  	at org.eclipse.persistence.internal.jpa.EJBQueryImpl.executeReadQuery(EJBQueryImpl.java:435)
  	at org.eclipse.persistence.internal.jpa.EJBQueryImpl.getSingleResult(EJBQueryImpl.java:772)
  	at org.eclipse.jubula.client.core.persistence.NodePM.findProjectID(NodePM.java:1022)
  	at org.eclipse.jubula.client.core.persistence.NodePM.getSpecTestCase(NodePM.java:926)
  	at org.eclipse.jubula.client.core.model.ExecTestCasePO.getSpecTestCase(ExecTestCasePO.java:260)
  	at org.eclipse.jubula.client.core.utils.TreeTraverser.traverseImpl(TreeTraverser.java:208)
  	at org.eclipse.jubula.client.core.utils.TreeTraverser.traverseImpl(TreeTraverser.java:198)
  	at org.eclipse.jubula.client.core.utils.TreeTraverser.traverseImpl(TreeTraverser.java:198)
  	at org.eclipse.jubula.client.core.utils.TreeTraverser.traverseImpl(TreeTraverser.java:198)
  	at org.eclipse.jubula.client.core.utils.TreeTraverser.traverseImpl(TreeTraverser.java:198)
  	at org.eclipse.jubula.client.core.utils.TreeTraverser.traverseImpl(TreeTraverser.java:198)
  	at org.eclipse.jubula.client.core.utils.TreeTraverser.traverse(TreeTraverser.java:303)
  	at org.eclipse.jubula.client.core.businessprocess.db.NodeBP.getOwningTestSuite(NodeBP.java:196)
  	at org.eclipse.jubula.client.ui.provider.labelprovider.decorators.TestDataDecorator.decorate(TestDataDecorator.java:57)
  	at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:269)
  	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81)
  	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
  	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365)
  	at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347)
  	at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371)
  	at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331)
  	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


If you close the error dialog you can continue working without any problems so Iḿ setting this severity to minor.
Comment 1 Alexandra Schladebeck CLA 2011-08-31 02:12:25 EDT 

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