[
https://issues.apache.org/jira/browse/MUSE-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589705#action_12589705
]
Rich Lucente commented on MUSE-270:
-----------------------------------
Hi Chris,
I tested the patch with my message broker. Other than the
AxisEnvironment.convertToDOM mentioned previously, I had no problems. On
multiple runs, I pounded my broker with 10,000 messages and I got all 10,000
back. The 5-10% message loss I was experiencing due to multi-threading is
gone! Thank you so much!
> 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: 270tsPatch2.txt, epr-tests.zip, muse_src.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]
