JNDI Binding for QueueConnectionFactory Disappears

[eusebio]

Hi

I'm running using JBoss 2.4.4. My message queue seems to be working fine (and has done for the past year) but recently we had a problem where the JNDI binding for the queue connection factory suddenly "disappears" to produce the following error:

NamingException
javax.naming.CommunicationException
[Root exception is java.rmi.ConnectException: Connection refused to host: <ip address>;
nested exception is:
java.net.ConnectException: Connection refused]

or

Error: NamingException
javax.naming.NameNotFoundException: RMIConnectionFactory not bound

Has anyone got any ideas about how this might be happening?

Thanks

[stephanenicoll]

what says the server.log file?
open the jmx console on the host to see what's happening (see if the naming service is registered)

[akirdat]

I have had services die on me before and usually it was because of load (i.e. too many threads running).
I found out exactly how many threads my JVM could create given my settings and OS. I then checked to see exactly under what circumstances was this limit reached. I found a few leaks in our code which was casuing idle threads to multiply and eventually choking some services.
Just my experience not to say that this is the problem you might be having.