[ 
https://issues.apache.org/jira/browse/MUSE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564130#action_12564130
 ] 

Chris Twiner commented on MUSE-270:
-----------------------------------

I was just given a new dual core laptop at work (core2 Duo, T7500 2.20Ghz).  As 
such I have run the tests again against my patched wholeMuseFixed.jar 5 times 
and it never misses a message (always 3000).  

With the normal must jars it gets NPE's and over 5 runs (messages out of 3000 
sent): 2468, 2549, 2522, 2617 and 2420.  Strangely the gap is much less on this 
new machine (was 1300-1500 on my other single cpu boxes).

I'm now confident that this fixes the EMPTY_DOC and Xerces NodeList issues.  
(Again the NodeList fix depends on Xerces never breaking nextSibling in an mt 
environment)

> EMPTY_DOC thread stability issues
> ---------------------------------
>
>                 Key: MUSE-270
>                 URL: https://issues.apache.org/jira/browse/MUSE-270
>             Project: Muse
>          Issue Type: Bug
>          Components: Utilities - General, QName, and XML, WS-Addressing and 
> SOAP
>    Affects Versions: 2.0.0 M1, 2.0.0 M2, 2.0.0, 2.1.0, 2.2.0, 2.3.0
>         Environment: Impacts all platforms and configurations
>            Reporter: Rich Lucente
>            Assignee: Dan Jemiolo
>             Fix For: 2.3.0
>
>         Attachments: epr-tests.zip, MuseThreadSafety.zip, WsnErrorsTest.zip
>
>
> This bug is being opened to track the EMPTY_DOC thread stability issue 
> currently being discussed on the muse-dev mailing list.  XmlUtils provides 
> EMPTY_DOC as a scratchpad instance of a DOM Document for creation of 
> elements.  This has been shown to cause exceptions in a multi-threaded 
> environment.  The issue is compounded by the widespread use of EMPTY_DOC in 
> the code due to its convenience and the reduction in object creation when 
> constructing XML fragments.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to