In my opinion, it would be good form for the producer.send() to throw exception when the exception notification reaches the client (understanding that since this is async operation, the client may send several messages before the exception reaches the client).
However, as long as the exception is thrown calling session.commit(), then the client is able to recover correctly. So yes, that would work. -- View this message in context: http://activemq.2283324.n4.nabble.com/Clients-not-receiving-ResourceAllocationException-in-transacted-sessions-tp4670862p4671054.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
