cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Ruby" <ru...@us.ibm.com>
Subject Re: ThreadSafe Parser
Date Wed, 31 Oct 2001 15:59:58 GMT
Berin Loritsch wrote:
>
> Sam, has Xerces fixed the concurrency issues with their Parser?  Basically
> what happened is the Parser could be reused until a SAXException happened
> (something about a class not being found or something weird like that),
> and once that SAXException happened, the Parser would always produce it.
> The load didn't have to be that high either (something like 10 concurrent
> requests every 300 ms [Apache JMeter]) would reproduce the problem.

My recollection of the discussion was that you asserted that there had been
a problem at one point, the xerces team asked for a test case, and the
discussion ended there.

Since you indicated that the problem was associated with an exception, I
decided that for Axis a simple expedient solution would be not to return
the parser to the pool if it threw an exception.  In other words, for the
99%+ case, we would get performance.  In the case where there is a
suspected problem, we get safety.

- Sam Ruby


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message