(URGENT) JBoss memory leak

Hi all,

We are using jboss-3.2.1_tomcat-4.1.24 version in Linux box with j2sdk1.4.2_01, and postgresql-7.3.4 as database. We allotted 1024MB memory to the deault instance. When it starts its taking only about 100 MBs. After some time the memory consumption will start to increase and with in 100 hrs, the whole memory will be exhausted. We are running the same application in another instance, that one is working fine for a very long time. Only this instance is eating up memory and eventually ends in OutOfMemoryError. Because of this we are forced to restart the application in every 50 hrs. We are using Apache 1.3 and mod_jk2 module to forward request to JBoss. Any one know what is happening ? We are not able to find the probelm or we dont know which way to proceed.

The only clue the JBoss left behind is this log

2005-03-13 22:45:40,680 ERROR [org.apache.tomcat.util.threads.ThreadPool] Caught exception executing org.apache.jk.common.SocketConnection@1e6e3cb, terminating thread
java.lang.OutOfMemoryError
2005-03-13 22:50:04,905 ERROR [org.jboss.ejb.plugins.LogInterceptor] Unexpected Error:
java.lang.OutOfMemoryError
2005-03-13 22:57:31,217 ERROR [STDERR] Unknown Response Type S ( this is from postgres)
2005-03-13 22:57:31,218 ERROR [STDERR] at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:123)
2005-03-13 22:57:31,218 ERROR [STDERR] at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:482)
2005-03-13 22:57:31,218 ERROR [STDERR] at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:461)
2005-03-13 22:57:31,219 ERROR [STDERR] at org.postgresql.jdbc1.AbstractJdbc1Connection.rollback(AbstractJdbc1Connection.java:1031)
2005-03-13 22:57:31,219 ERROR [STDERR] at org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.rollback(LocalManagedConnection.java:116)
2005-03-13 22:57:31,219 ERROR [STDERR] at org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.rollback(TxConnectionManager.java:859)
2005-03-13 22:57:31,219 ERROR [STDERR] at org.jboss.tm.TransactionImpl.rollbackResources(TransactionImpl.java:1648)
2005-03-13 22:57:31,219 ERROR [STDERR] at org.jboss.tm.TransactionImpl.rollback(TransactionImpl.java:448)
2005-03-13 22:57:31,219 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:361)
2005-03-13 22:57:31,219 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:253)
2005-03-13 22:57:31,219 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:74)
2005-03-13 22:57:31,219 ERROR [STDERR] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:92)
2005-03-13 22:57:31,220 ERROR [STDERR] at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:120)
2005-03-13 22:57:31,220 ERROR [STDERR] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93)
2005-03-13 22:57:31,220 ERROR [STDERR] at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:477)

If any one can give any clue or suggestion , it would be great help.
Thanx in advance,
Sanju.

Can't say without knowing a lot more about you application what might be causing this. You could profile the app and try to spot where a memory leak is occuring. If its really that urgent, you should contact JBoss and pay for their support.

Paul,

Is there any good tool available to monitor the memory usage of the application ? We are not thinking that the problem is with application because, the same application is running on another instance for very long time and it does not any sort of problem. If you need more infos about the application, well I can give it.

Wow, 3.2.1 with tomcat 4. That is old. It's entirely possible that it is an old 3.2.1 issue. You might try testing on a later version to see if the problem still exists. Beyond that, I'm with Paul. It sounds like you need a support contract.

Yes we are also thinking on the same line. But right now we are not in a position to upgrade it.