commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Russell Neufeld <>
Subject JXPath concurrency exceptions
Date Wed, 09 Jun 2004 22:47:35 GMT
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
getValue() calls on the DOM to get configuration values.  That all works great except under
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.


      at java.util.HashMap$HashIterator.nextEntry(
      at java.util.HashMap$
      at org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.cleanupCache(
      at org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.compileExpression(
      at org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getValue(
      at com.ris.common.Configuration.getProperty(

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message