Good morning all, We are experiencing a rather severe memory leak issue in the use of the DocumentImpl class (whether it be the org.apache.xerces.dom.DocumentImpl or the com.sun.org.apache.xerces.internal.dom.DocumentImpl class) with regards to the userData property.
During our (simplified) testing, I have observed that the number of DocumentImpl objects grows from 9 instances after a single call to at least 48 after 50 calls of a service. In addition, one particular DocumentImpl object grows from 99 kb of retained heap to 156kb of retained heap after 50 calls, with a forced garbage collection not reducing the size at all, growing at a rate of ~ 1.2kb of retained heap per call. Upon further inspection, the userData table contains numerous copies of WSDL Element nodes (one brief inspection showed at least 4 copies of each claimType in our simple test). I'm not sure if this property grows as a percentage rate of the WSDL size (our WSDL is 12K, 1.2k being 10%) making larger WSDLs leak memory at a much more rapid rate or if the retained heap will grow at a constant rate regardless of WSDL size but given the contents I would suggest it is a function of WSDL size. As an example of how serious this can become, our production service which brought this to our attention had, at one point, over 500 MB of retained heap in a single DocumentImpl userData property, with over 1 million objects in the table. Is this a known issue? Is there a common configuration issue which may cause this? Thanks, Dan. -- View this message in context: http://cxf.547215.n5.nabble.com/Potential-Memory-Leak-tp5735592.html Sent from the cxf-user mailing list archive at Nabble.com.
