This continues for a while then eventually I get exception saying could not connect. I guess at that point I've exhausted the connections in the client pool.

However, before I get the could not connect exception, there is a long period where I can still send JMS messages, yet they never end up on my queue. No JMSException reported either.

My installation was running fine for the last month under this codebase and only recently started showing this problem. I guess the real problem is that something has changed in our network and as a result control connections are experiencing problems. I will investigate that issue our side, but it exposed what looks like a bug in JBoss Messaging / JBoss Remoting.

I've modified my bisocket configuration from config listing 1 to config listing 2 and it seems to be behaving better. I could try updating to a later version of the JBM/JBR libraries... but only want to do so if I can find the Jira marking the issue as closed.

Thanks for the update. I took a chance last week and did exactly that (config listing 2 from previous forum was modified from JBM 1.4.0.SP3) and after 5 days in production the problem hasn't shown itself again. Looks like the updated config does indeed do the job as you suggest.

PS. The only other change was to make sure I still refer to the older "clientMaxPoolSize" attribute instead of the newer "JBM_clientMaxPoolSize". I may have overcompensated a bit with this figure (1ooo instead of default 200), but haven't had problems.