*Hello. Just make sure that the client app and the server run on two different machines. Then deactivate the network interface on the client machine. That works fine for me.
Just removing the hard connection to the app server will not reproducing the problem that is being described. With your client running, go to the jmx console and stop the queue. The client exception listener will NOT detect that the queue is gone.
If anyone has a work-around from this problem, please post a solution.
is starting/stopping the queue the only way to simmulate a connection failure ?
Thanks in advance