Hi Robbie, While I am using - *forceSyncSend=true* and with a CompletionListener, I would expect the callback event to come on the same thread that invoked the send(), however in my observation - I am sending the message using the main thread and I am getting a response on to the JmsSession [ID:12c9fd67-aed5-4930-8da2-31cb3f99729d:1:1] completion dispatcher and that means any exception arising from the send() operation will not be propagated to the main thread.
*Is this behavior correct?* Does that mean that the difference of behavior between Sync and Async is the callback of onCompletion() or onException() and nothing more...(as both are working on their own threads) and only the server side code would be able to understand the notification/exception but will not be able to propagate it to the client....!!!! Attached is the code - TestQpidSendSync.java <http://qpid.2158936.n2.nabble.com/file/t396358/TestQpidSendSync.java> /Steps to reproduce/ - 1. Start the main 2. Terminate the connection to the service bus while the main thread is running 3. it will attempt couple of times before throwing exceptions in the CompletionListener's onException() -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
