[ https://issues.apache.org/jira/browse/DIGESTER-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230186#comment-13230186 ]
Simone Tripodi commented on DIGESTER-163: ----------------------------------------- two loaders created by different threads *have to* be allowed, of course, that is why we are investigating about the problem. I am testing your modifications right now, I hope to let you know good news ASAP :) > ConcurrentModificationException creating a new Digester via > loaderInstance.newDigester() > ---------------------------------------------------------------------------------------- > > Key: DIGESTER-163 > URL: https://issues.apache.org/jira/browse/DIGESTER-163 > Project: Commons Digester > Issue Type: Bug > Affects Versions: 3.2 > Environment: Linux, JDK 6 > Reporter: Torsten Krah > Attachments: Digester163TestCase.java > > > I am gettig a ConcurrentModificationException when trying to create new > Digester instance from a configured loader: > Trace is: > {code} > java.util.ConcurrentModificationException: null > at > java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:761) > ~[na:1.6.0_27] > at java.util.LinkedList$ListItr.next(LinkedList.java:696) ~[na:1.6.0_27] > at > org.apache.commons.digester3.binder.FromBinderRuleSet.addRuleInstances(FromBinderRuleSet.java:130) > ~[commons-digester3-3.2.jar:3.2] > at > org.apache.commons.digester3.binder.DigesterLoader.addRules(DigesterLoader.java:581) > ~[commons-digester3-3.2.jar:3.2] > at > org.apache.commons.digester3.binder.DigesterLoader.newDigester(DigesterLoader.java:568) > ~[commons-digester3-3.2.jar:3.2] > at > org.apache.commons.digester3.binder.DigesterLoader.newDigester(DigesterLoader.java:516) > ~[commons-digester3-3.2.jar:3.2] > at > org.apache.commons.digester3.binder.DigesterLoader.newDigester(DigesterLoader.java:475) > ~[commons-digester3-3.2.jar:3.2] > at > org.apache.commons.digester3.binder.DigesterLoader.newDigester(DigesterLoader.java:462) > ~[commons-digester3-3.2.jar:3.2] > {code} > The binder documentation (employee servlet) and the mailing list did confirm > to me, that the loader should be safe to be shared, so this should not happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira