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

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

This is indeed necessary, I'll make another patch later today I hope.

Any code used in osgi that does "spi" type lookup will have this grief.  The 
Context classloader is evil :-).

Also for any one searching Jetty's (I also imagine other j2ee servers do this) 
recieving threads also set the context classloader to their webcontext's 
classloader.  This is the root cause of this, and other, osgi related problems. 
 Again for completeness this was also detected running a heavily patched axis 
1.4 and muse (with 270) inside of an equinox osgi container (using the 
httpservlet bridge).

> 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]

Reply via email to