useAsyncSend will force the producer to send asynchronously even if the message is persistent. This may not be desired as the client won't wait for the broker to respond with an Ack saying the message is persisted in the store.
You could try lowering the inactivity monitor. The default is 30000. ?wireFormat.maxInactivityDuration=30000 See here: http://activemq.apache.org/activemq-inactivitymonitor.html On Mon, Dec 3, 2012 at 1:52 PM, kevin_405 <[email protected]> wrote: > > Found a work around > > Looks like if use jms.useAsyncSend=true for the broker url it then the > producer does not wait until send is complete. > > e.g. > > failover:(tcp://localhost:61616,tcp://localhost:61616)?jms.useAsyncSend=true&jms.redeliveryPolicy.maximumRedeliveries=1&timeout=3000 > > > I am curious about the implications of this change.. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Send-Timeout-does-not-work-while-simulating-packetloss-tp4660111p4660126.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
