[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xalan-dev
Subject:    [jira] [Created] (XALANJ-2600) Memory leak in TransformerIdentityImpl
From:       Samuel_Brezáni_(JIRA) <jira () apache ! org>
Date:       2016-02-20 11:46:18
Message-ID: JIRA.12940772.1455968769000.101143.1455968778243 () Atlassian ! JIRA
[Download RAW message or body]

Samuel Brez=C3=A1ni created XALANJ-2600:
--------------------------------------

             Summary: Memory leak in TransformerIdentityImpl
                 Key: XALANJ-2600
                 URL: https://issues.apache.org/jira/browse/XALANJ-2600
             Project: XalanJ2
          Issue Type: Bug
      Security Level: No security risk; visible to anyone (Ordinary problem=
s in Xalan projects.  Anybody can view the issue.)
          Components: Xalan
    Affects Versions: 2.7.2
            Reporter: Samuel Brez=C3=A1ni
            Assignee: Steven J. Hathaway


Hi.

I found a serious memory leak in the Xalan library. It is caused by the org=
.apache.xalan.transformer.TransformerIdentityImpl class.

I try to explain mechanism how the memory leak is caused:

Web application is deployed on SAP NetWeaver AS with Java 1.6 (1.6.0_95). T=
he application uses Spring WS library but also another libraries with depen=
dency to Xalan library.

When the web service is invoked, then the TransformerIdentityImpl class is =
used. This class is used because it's extends javax.xml.transform.Transform=
er and it is created by Java core method - javax.xml.transform.TransformerF=
actory.newInstance().


A class com.sun.xml.internal.messaging.saaj.soap.EnvelopeFactory is used fo=
r handling web services. This object also contains cache (ParserPool) with =
SAXParser objects (com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl). =
As key for this cache is used an application class loader.

EnvelopeFactory object and SAXParserImpl objects are loaded by a system cla=
ss loader, but TransformerIdentityImpl class is loaded by an application cl=
ass loader.

During handling of web service a method org.apache.xalan.transformer.Transf=
ormerIdentityImpl.transform(Source, Result) is invoked. This method uses SA=
XParser as a reader. Problem is that this method register self for handling=
 properties (eg: "http://xml.org/sax/handlers/DeclHandler") but after proce=
ssing method doesn't unregister self from SAXParser. It means that objects =
loaded by the system class loaded has dependencies on objects loaded by the=
 application class loader.

Objects are still loaded after application is undeployed because cached SAX=
Parser references TransformerIdentityImpl.


I prepared very simple patch to fix this problem. In the attachment is also=
 picture which demonstrates situation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]