Forwarding on behalf of the ASF's Travel Assistance Committee.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E-mail: mrgla...@apache.org
"Gavin McDonald" wrote on 06/06/2011 04:03:24 AM:
> The Apache Software Foundation (ASF)'s Travel Assistance Commit
All,
My team has built a web application that has a few components that rely heavily
on the xerces DOM implementation. Unfortunately a lot of this was developed
before we even learned that the node implementations are deliberately not
thread safe. =) I've added a few sync blocks where appropr
On Wed, Jun 8, 2011 at 1:47 AM, Newman, John W wrote:
> 1) Under very high load
What exactly is "high load" in your case? Is it number of users using
your applications, number of threads sharing your objects or what?
> an element will somehow lose nearly all of its children.
This may be du
Hi John,
None of Xerces' DOM implementations are thread-safe, even the non-deferred
ones. This is true even for read operations. In particular, the
implementation of the NodeList methods (i.e. item() and getLength()) are
not thread-safe. These methods do some internal writes to a cache which are
Hi Mukul,
Mukul Gandhi wrote on 06/08/2011 12:02:59 AM:
> > 2) Also under high load, I occasionally get this stack trace
(this is
> > not the cause of or symptom of item 1, it is a separate issue occurring
at
> > separate times)
>
> > java.lang.NullPointerException:
> > (no message)
> > a
On Wed, Jun 8, 2011 at 9:48 AM, Michael Glavassevich
wrote:
> No, I'm 99.99% sure this is a threading issue. ParentNode.nodeListItem() is
> one of several places you can get a NullPointerException if you don't
> synchronize.
>
> There's really no other way to get an NPE there. The application is m
