Re: connection.close(), on a brokenConnection resolves my problem

"Multicast Discovery Agent Notifier" daemon prio=10 tid=0x0a82dc00 nid=0x6586 waiting on condition [0x43188000..0x43188b90] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x2aaab3cf20a8> (a

Re: connection.close(), on a brokenConnection resolves my problem

I think this session is associated to the network of broker topology between (multicast) my two "equivalent processes". I think I have several problems. However Close() seems to let the process in a cleaner situation. Here it is an other problem where "multicast" network of brokers are broken wh

Re: connection.close(), on a brokenConnection resolves my problem

Unfortunately, all my problems are not resolved ... I tried with two equivalent processes on two different servers (and the third which is abruptly closed). One terminated gracefully, the other had always 2 active threads "ActiveMQ Session: ID:td0sib01s.priv.atos.fr-46825-1246630520929-0:2:3" pri

connection.close(), on a brokenConnection resolves my problem

NEW If I force a brokenConnection.close() into the onException callback, (called when the "other" connection is broken), my process can now terminate gracefully and is not blocked waiting threads die. However there is a JMSException thrown by this "close" on a brokenConnection. But it is not a b