With the async property what i do find is that the message is persisted in the local store and then when the Active MQ link is restored the message goes from the producer/broker to ActiveMQ server and then to the received.
This works for me as the only message loss is see is if my producer server goes down. I had already tried maxInactivityDuration the solution u suggested before going with the async.. The max inactivity works some times but not all the time.. Async responds quickly all the time.. my system being a real time system , performance is most important. The jms message if lost have minor billing implication which is not as catastrophic as system performance impacts. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Send-Timeout-does-not-work-while-simulating-packetloss-tp4660111p4660163.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
