DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11125>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11125 Threading issue can cause NPE in DOM Summary: Threading issue can cause NPE in DOM Product: Xerces2-J Version: 2.0.2 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: DOM AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In the method "Node nodeListItem(int index)" in ParentNode.java it calls "ownerDocument.getNodeListCache(this);". To set the variable "fNodeListCache". In CoreDocumentImpl.java in the method "NodeListCache getNodeListCache (ParentNode owner)" it may set the "fNodeListCache" to null. These lines could cause the problem: if (c.fOwner != null) { c.fOwner.fNodeListCache = null; } c.fOwner = owner; Under heavy load with many threads it is possible to the "fNodeListCache" to be null and cause a null pointer exception in ParentNode.java. Does it need to set the variable to null when it will be set a few lines later? Where else is this method being called? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
