I am seeing what I believe is the same. 

Environment in this case using:
JBoss Messaging 1.4.0.GA
JBoss Remoting  2.2.2.SP1

Seeing the following warning:

2008-02-18 13:53:43,993 WARN  
[org.jboss.remoting.transport.bisocket.BisocketServerInvoker] [EMAIL 
PROTECTED]: detected failure on control connection Thread[control: 
Socket[addr=/10.140.177.50,port=58029,localport=1654],5,main] 
(a3w4x10-9m4crq-fcsan8o9-1-fcsan9pl-9: requesting new control connection
  | 2008-02-18 13:53:43,993 DEBUG 
[org.jboss.remoting.transport.bisocket.BisocketClientInvoker] getting secondary 
locator
  | 

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.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130498#4130498

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130498
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to