org.jboss.wsf.stack.jbws.EndpointServlet - memory issue

[bfp]

I am running a JBoss 2.7.1 as a producer over WSRP. Under load I experience a memory issue with the below details:

"One instance of "org.jboss.wsf.stack.jbws.EndpointServlet" loaded by "org.jboss.mx.loading.UnifiedClassLoader3 @ 0xcbfd5bc0" occupies 124,724,728 (25.20%) bytes. The memory is accumulated in one instance of "java.util.LinkedList$Entry" loaded by "<system class loader>".

Keywords

org.jboss.wsf.stack.jbws.EndpointServlet

org.jboss.mx.loading.UnifiedClassLoader3 @ 0xcbfd5bc0

java.util.LinkedList$Entry"

The Tenured generation is not cleaned up due to this issue and the memory consumption is quite linear in growth and unstopable.

Below is the shortest path to the acumulation point

java.util.LinkedList$Entry @ 0xd71eb970	24	124,724,656
header java.util.LinkedList @ 0xd71eb958	24	124,724,680
\ preDestroyRegistry org.jboss.wsf.stack.jbws.EndpointServlet @ 0xd71eb930	40	124,724,728
.. <Java Local> java.lang.Thread @ 0xdba14690 ajp-0.0.0.0-8010-28 Thread	112	307,552
..+ instance org.apache.catalina.core.StandardWrapper @ 0xcf1b5d40 »	216	1,608
..+ servlet org.apache.catalina.core.ApplicationFilterChain @ 0xdb7dd370 »	32	88
..\ Total: 3 entries

Environment setup:

running on JDK 1.6

JBoss Portal 2.7.1 (as a WSRP producer) with JBoss AS 4.2.3 (with jbossws-native-3.1.0 - default)

AJP, MOD_JK

Regards,

@Bob

[ropalka]

Either switch to JBossAS 7.0.1 or JBossAS 6.1.0.

[bfp]

Hi Richard,

Thank you for your reply.

We are using JBoss portal 2.7.1 which is based on JBoss AS 4.2.3, and the EndpointServlet from the jbossws-native-core is similar with the revision from 8819 from SVN:

http://source.jboss.org/browse/JBossWS/stack/native/trunk/modules/core/src/main/java/org/jboss/wsf/stack/jbws/EndpointServlet.java?r=8819

I have looked in the JIRA for some coments related to the fixes that were done against the Endpoint but I wasn't able to find some coments to confirm that the issue we have is fixed by one of the next revisions. Could you please clarify if that was a known issue on that part ?

The object which I found in the memory is the "preDestroyRegistry" which holds the LinkedList and should be cleanup by the "destroy()", which aparently is not cleaning up, or it is not trigered.

Kind regards,

@Bob

[ropalka]

Hi Bob,

   Both JBossAS 6.x & JBossAS 7.x series are using different SOAP stack.

We used to have JBoss Native (which you are using via JBossAS 4x), but this

stack was deprecated and we're using Apache CXF SOAP stack instead.

I highly suggest you to switch to up2date JBossAS version.

Richard

[bfp]

After some searches my case was resolved by using the jbossws-native-3.0.4. From jbossws-native-3.0.5 the issue was introduced and resolved in jbossws-native-3.1.1 which unfortunatelly introduced a side effect, hence 3.0.4 did the fix.

[vaidya_onkar]

Hi Bogdan

Where can I find jboss-native-3.0.4 distribution?

I did not find it here: http://www.jboss.org/jbossws/downloads.

Obviously I can't move away from JBoss 4.2.3 GA as yet.

[bfp]

Hi,

You need to download the source code and compile it.

Here you find the tags for the releases;

http://anonsvn.jboss.org/repos/jbossws/stack/native/tags/

Here you find an overview of the repository:

http://www.jboss.org/jbossws/sourcecode

Kind regards,

@Bob