2 Replies Latest reply on Jan 19, 2010 4:39 AM by slimamar

Sockets left in CLOSE_WAIT on server for JMS connections

slimamar Jan 18, 2010 11:29 AM

Hi,

We 're using JBoss AS 5.1.0.GA (with JBoss Messaging) and a client close a JMS connection
a socket is left in the CLOSE_WAIT state on the server.
We then quickly run out of file descriptors because of all the CLOSE_WAIT sockets left open.

Is the same problem with :
http://community.jboss.org/message/368512#368512

How can we resolve this issue ?

Thanks in adavance.

1. Re: Sockets left in CLOSE_WAIT on server for JMS connections

gaohoward Jan 18, 2010 9:49 PM (in response to slimamar)

Hi,

We recently found an issue that i believe closely related to yours. It's still being investigated. You can try to work around it by setting timeout to a non-zero value.

By the way if you are using JBM 1.4.3.GA, I suggest you to update to 1.4.6.GA. There is a good article about how to do it written by a user. Search the forum you will find it.
Actions
2. Re: Sockets left in CLOSE_WAIT on server for JMS connections

slimamar Jan 19, 2010 4:39 AM (in response to gaohoward)

Thanks for your response.

Setting timeout to a non non-zero value (file remoting-bisocket-service.xml) does not resolve the problem.

I'm going to update to JBM 1.4.6.GA and JBoss Remoting 2.5.2SP1.
Actions

Go to original post