JBossMQ Thread Count grows until Linux Too Many Files Open e

thancock May 10, 2005 10:03 AM

We are using JBoss 3.2.6 on JVM 1.4.2-06.

We have 2 web servers that publish messages onto one of 3 JBoss Message Queue servers.

The Thread List shows lots and lots of the following entries in the JBossMQ Thread Group:

Thread: UIL2.SocketManager.ReadTask#5 client=10.2.11.3:38834 : priority:5, demon:true
Thread: UIL2.SocketManager.WriteTask#6 client=10.2.11.3:38834 : priority:5, demon:true

interspersed with a few:

Thread: Thread-63 : priority:5, demon:true

The IP address relates to one of the servers publishing on the queue. The publishing of the message onto the queue is successful and no errors are thrown.

Does anyone know why the socket is never treated as disconnected, thus freeing the Thread for re-use? Or is there a configuration setting for Thread timeouts?

We have to restart the servers about once every 2 hours to avoid the open files limit on the Linux boxes we are running and it would be great if we could avoid this problem altogether.

1. Re: JBossMQ Thread Count grows until Linux Too Many Files Op

gustavo.lima Sep 8, 2005 8:50 PM (in response to thancock)

Hi,

we are having the same problem. Do you resolve it? How?
Actions
2. Re: JBossMQ Thread Count grows until Linux Too Many Files Op

thancock Sep 11, 2005 6:18 PM (in response to thancock)

Unfortunately we received no help with this problem. We checked all connections and objects were being closed and destroyed and still the sockets on each MDB remained.

The only solution for us was to move these tasks away from the MDB to a servlet which received the object, fired off a new Thread and processed the object in the Thread destroying the Thread when it was finished.

It works well for us but what would have worked better would have been a solution in an existing framework (rant, rant, rant - lol).
Actions

Go to original post