activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <>
Subject Re: Configuring ActiveMQ for reliability
Date Tue, 06 May 2014 17:36:00 GMT
Can you put together a test that shows message loss? I can help you
debug it and find the fix if there is indeed message loss as seen by
the broker.

On Mon, May 5, 2014 at 1:59 AM, Robin Kåveland Hansen
<> wrote:
> Hi,
> Vi have been running ActiveMQ-5.6.0 in production since january last year and
> we’ve been looking to upgrade to a newer version for a while. Our main
> requirement is reliability and we run the broker with jdbc persistence against
> Oracle.
> However for the last few version upgrades we have attempted we have been
> able to find message loss scenarios that hit versions newer than 5.6.0.
> At this point we’re running out of ideas, it seems that we can not come up
> with a configuration for 5.7.0, 5.9.0/1 brokers that does not have message
> loss in the following scenario:
> - Start batchjob that produces a few thousand messages with client A
> - Messages are consumed by client B who posts them to C
> - Let C consume a few hundred
> kill -9 C
> kill -9 activemq
> B and C have audit.
> We’ve also been able to cause message loss in ‘nicer’ scenarios (TERM
> instead of KILL) in other ways. Clearly we seem to be missing something
> here, because it works fine with 5.6.0 (unless the client runs > 5.7.0). We
> sometimes observe duplicate messages with 5.6.0, but this is fine.
> On the broker, the following is set for all queues:
> producerFlowControl=“false"
> queuePrefetch=“1"
> optimizedDispatch=“true”
> We are using transacted clients (these are configured with camel). We have
> tried various permutations of the following options on ActiveMQConnectionFactory:
> optimizeAcknowledge
> alwaysSyncSend
> dispatchAsync
> sendAcksAsync
> We also ensured that we’re sending with the appropriate delivery mode (2).
> Are we missing something? Does anyone have tips for us?
> --
> Kind regards,
> Robin Kåveland Hansen

Christian Posta
twitter: @christianposta

View raw message