Memory leak in JBoss Messaging 1.4.0SP3-CP02

[j.hedin]

We have found a memory leak in JBoss Messaging 1.4.0SP3-CP02 on JBoss 4.2.2.GA + JBoss remoting 2.5.0SP1. We have nailed it down to the opening and closing of a non transacted JMS connection factory within a JTA transaction. The reason we need this is that we do send JMS messages to a singleton service in the cluster within a transaction and react on the reply. We have not been able to find any suggestion to fix in Jboss messaging, but a workaround with no memory leak.


Pattern:

Memory leak:

MDB in JTA XA-transaction -> jBPM -> EJB3 SLSB -> Send JMS via JNDI name "ConnectionFactory" in no TX mode


No leak:

MDB in JTA XA-transaction -> jBPM -> EJB3 SLSB -> EJB3 SLSB with REQUIRES NEW transaction attribute -> Send JMS via "java:/JmsXA"

[ataylor]

Ok, any chance you can test with jboss 4.2.3.GA to see if you get the same result.

[timfox]

JBoss 4.2.2.GA + JBoss remoting 2.5.0SP1 is not a tested/supported combination.

The correct version of remoting to use with the version of JBM is detailed in the user guide - install section - of the JBM release you are using.

If you use any other version I make no claims of whether it will or won't work.

[j.hedin]

Initial test indicates the leak is not present in JBoss 4.2.3. I will post more long term test soon.


The reason for JBoss remoting 2.5.0SP1 is that we need servlet invoker for both EJB3 SLSB and JMS, since we can not open more ports in the firewalls. As I understood it, this is not supported in JBoss remoting 2.4.

[pratimkm]

We are running jboss-messaging-1.4.2.GA-SP1 on Jboss AS 4.2.2GA. We also have a similar situation where a transacted stateless session EJB is having a non transacted JMS connection . Our application is quite big for testing with Jboss profiler. Any idea whether it can cause a memory leak ? Thanks in advance.