[
https://issues.apache.org/jira/browse/MUSE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557975#action_12557975
]
Chris Twiner commented on MUSE-270:
-----------------------------------
Hi Vinh,
Could you please try the patched muse.jar and the test cases I attached mid
october to see if they solve this issue (I got rid of EMPTY_DOC and the
nodeList issue). I still however don't have access to an smp or multi-core
computer on which to test this out.
As of yet I have had zero feedback on the patch, please note that this still
occurs on a single threaded cpu / system. The test case I posted runs on a
single cpu and attempts to prove/fix the threading issues regarding EMPTY_DOC.
Its not really a concern of mine if my solution is chosen as workable, just
that its proven correct / incorrect and is discussed. So far since no
discussion has taken place on it I have no idea if it truly works.
This must be solved for muse to be used seriously in any production 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]
