Issue 21 in warp-persist: Track down ConcurrentModificationException when running tests
codesite...@google.com
Owner: robbie.vanbrabant
Labels: Type-Defect Priority-Medium
New issue 21 by robbie.vanbrabant: Track down
ConcurrentModificationException when running tests
http://code.google.com/p/warp-persist/issues/detail?id=21
I haven't been able to reproduce it, but once I got:
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at
org.hibernate.connection.DriverManagerConnectionProvider.close(DriverManagerConnectionProvider.java:152)
at org.hibernate.impl.SessionFactoryImpl.close(SessionFactoryImpl.java:801)
at
com.wideplay.warp.hibernate.ClassLevelManagedLocalTransactionsTest.post(ClassLevelManagedLocalTransactionsTest.java:79)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
Labels: Milestone-Release2.0
Comment #1 on issue 21 by robbie.vanbrabant: Track down
ConcurrentModificationException when running tests
http://code.google.com/p/warp-persist/issues/detail?id=21
(No comment was entered for this change.)
codesite...@google.com
Comment #2 on issue 21 by dhanji: Track down
http://code.google.com/p/warp-persist/issues/detail?id=21
Could be the order in which tests are run--if for instance a cleanup failed
to run for some reason. The
integration tests are not parallelizable, unfortunately (pretty much all wp
tests).
I would not report this until you can reproduce it.
codesite...@google.com
Status: WontFix
Comment #3 on issue 21 by robbie.vanbrabant: Track down
ConcurrentModificationException when running tests
http://code.google.com/p/warp-persist/issues/detail?id=21
Haven't seen it since.