-
1. Re: Memory Leaks in JBoss 3.0.0
joelvogt Oct 30, 2002 6:40 PM (in response to coughlam)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.
-
2. Re: Memory Leaks in JBoss 3.0.0
coughlam Nov 1, 2002 7:21 AM (in response to 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 -
3. Re: Memory Leaks in JBoss 3.0.0
yamax Nov 8, 2002 12:28 PM (in response to coughlam)It looks like you are using JBoss MQ (are you ???) which has known memory leaks, and should be fixed in 3.0.4
nitin