Description of problem: Customer wants to use setExceptionListener and onException method to implement re-connect logic after getting an exception indicating the connection with the broker has disconnected. I am able to receive messages OK, but when I do "service rhmd stop" the onException method is not called. The program continues to run, and gives no indication that the connection is closed. Should stopping the broker cause onException to be called in my program? Is there any other way to close the connection and test the re-connect logic? The exception handler must deal with orderly and disorderly disconnects, e.g. due to broker crash, network failure etc.
The exceptions were not propogated properly to the JMS Layer (not implemented). I have fixed that in Apache Qpid trunk rev 616542. We also need to detect a network connection drop and notify the qpid layer, so it can be passed to the JMS layer. This is also not implemented yet.
qpid-java-common-0.2-9 and qpid-java-client-0.2-9 have been pushed to the staging repo for testing