Memory Leaks in JBoss 3.0.0

[coughlam]

Hi,
I have a J2EE enterprise application running on JBoss 3.0.0 with Tomcat running externally ( separate VM ). The application uses Servlets, Stateful and stateless EJB's, JMS and Message Driven beans. It connects to a MySQL database using a Connection pool managed by JBoss.

The application basically processes XML documents, parses them , makes changes, puts it into the database, then spits the modified version out the end.


Functionally, the application works fine on JBoss, however under load testing, the JBoss Server seems to leak, approximately 750Kb of memory with every document sent through( each only 3kb in size !!). When I run the same application with the same source code, same database on an eval of BEA Weblogic, there are no memory leaks !

Has anyone else experienced these problems with the JBoss 3.0.0 server ??

Thanks,
Mick

[joelvogt]

3.0.0 was the first 3 release and as you expect things have quickly gotten a lot better since then. Try a later version and see if you have better luck.

[coughlam]

Hi,
I tried the same application on Version 3.0.3 with Tomcat embedded and I got the same results.

I find that after the application has run I get a exception from JBoss code:

javax.ejb.EJBException: Could not passivate; CausedByException is:
org.jboss.mq.il.oil.OILClientILService
at org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:293)
at org.jboss.ejb.plugins.StatefulSessionInstanceCache.passivate(StatefulSessionInstanceCache.java:78)
at org.jboss.ejb.plugins.AbstractInstanceCache$1.execute(AbstractInstanceCache.java:615)
at org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:206)
at java.lang.Thread.run(Thread.java:484)
java.io.NotSerializableException: org.jboss.mq.il.oil.OILClientILService
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)


If JBoss can't passivate some of its components, maybe it can't retreive some memory ??

Mick

[yamax]

It looks like you are using JBoss MQ (are you ???) which has known memory leaks, and should be fixed in 3.0.4

nitin