You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@xalan.apache.org by bu...@apache.org on 2003/02/27 04:30:12 UTC

DO NOT REPLY [Bug 17461] New: - Thread DeadLock situation

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=17461>.
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=17461

Thread DeadLock situation 

           Summary: Thread DeadLock situation
           Product: XalanJ2
           Version: 2.0.4
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Major
          Priority: Other
         Component: org.apache.xalan.transformer
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: srikarmuthineni@yahoo.com


Hi,
Iam using weblogic 6.1 sp2's servlet container.
Iam using Xlan.jar in my classpath to tranlate my XML documents.
I've observed weblogic hanging , if the concurrent requests on the servlet is 
more than the weblogic active thread count(which can be configured).
After analysing the thread dump of weblogic we concluded Xlan.jar is causing 
some thread deadlock condition within weblogic.
For each request I create a new instance of transformer like..
"TransformerFactory tFactory = TransformerFactory.newInstance();"
If I bypass xlan.jar usage then things are normal.
Any insight?
TIA