Russ, I think we had this issue a long time ago. I thought I'd fixed it. Are you using the current code base? It can be found at
http://cvs.apache.org/builds/jakarta-commons/nightly/commons-jxpath/ - Dmitri ----- Original Message ----- From: "Russell Neufeld" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 09, 2004 6:47 PM Subject: JXPath concurrency exceptions > Hi all, > > I've been using jxpath v1.1 to implement a central store of system configuration backed > by an XML document. I read the XML document into a DOM tree and then execute a series of jxpath > getValue() calls on the DOM to get configuration values. That all works great except under heavy > load, say 100 threads looking for config values. Every so often I get the following exception. > Do all calls to getValue() need to be synchronized? That would be unfortunate. Is there any > alternative? Is this a bug that's fixable in the jxpath source? > > Thanks. Love jxpath by the way. > > Russ > > > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:-3) > at java.util.HashMap$EntryIterator.next(HashMap.java:905) > at org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.cleanupCache(JXPathC ontextReferenceImpl.java:270) > at org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.compileExpression(JX PathContextReferenceImpl.java:-3) > at org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getValue(JXPathConte xtReferenceImpl.java:-3) > at com.ris.common.Configuration.getProperty(Configuration.java:-3) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
