Please try an upgrade to 5.9 to begin with.
On Dec 6, 2013, at 11:08 AM, badrinana wrote:
> Can someone help me out what other settings other than trackMessages=true or
> enableAudit="true" or auditNetworkProducers="true" can be used?
>
> I have tried all the above settings & I am still getting
Can someone help me out what other settings other than trackMessages=true or
enableAudit="true" or auditNetworkProducers="true" can be used?
I have tried all the above settings & I am still getting duplicate messages
replayed.
Should I upgrade from Active MQ 5.5 to Active MQ 5.9 instead of upgra
I tried setting trackMessages=true. Still I get duplicate messages.
failover:(${jms.broker1.uri},${jms.broker2.uri})?randomize=false&jms.prefetchPolicy.queuePrefetch=1&maxReconnectAttempts=-1&trackMessages=true
I also added auditNetworkProducers in the tran
1 - Correct.
2 - I actually haven't used that myself, I'd give it a whirl.
3 - To commit yourself you need to change the Ack mode, this is how
you'd do batches for example with transacted mode.
On Dec 5, 2013, at 10:20 AM, badrinana wrote:
> Hi Johan,
>
> I am assuming if I don't explicit
Hi Johan,
I am assuming if I don't explicitly add acknowledge=auto in the spring.xml,
all messages should ideally be Acked automatically. 1) Is the assumption
right?
Reading this jira: https://issues.apache.org/jira/browse/AMQ-3576
auditNetworkProducers - network issues / possible stuck
That is the default setting -
Session.AUTO_ACKNOWLEDGE
On Dec 4, 2013, at 3:01 PM, badrinana wrote:
> Hi Johan
>
> Do I need to add acknowledge="auto" in the tag?
>
> class="org.springframework.jms.listener.DefaultMessageListenerContainer">
> According to example in blog:
> http://bsnyderbl
Hi Johan
Do I need to add acknowledge="auto" in the tag?
According to example in blog:
http://bsnyderblog.blogspot.com/2010/05/tuning-jms-message-consumption-in.html
The example has acknowledge="auto". I am wondering if I need to add this
explicitly in my configuration.
Thanks
Badri
--
View
Yes. I feel this is an error & not expected behavior. The first message was
processed successfully by my consumer at 12:04:11.002 PM. There were no
network or database issues or failover which took place between 12:04 to
12:21. At 12:22, I restart Active MQ and immediately lots of such messages
get
Was this actually an error and not expected behavior?
I.e this could have happened for several reasons, like a delayed
ack that never hit AMQ as it was doing failover.
On Dec 3, 2013, at 3:34 PM, badrinana wrote:
> I upgraded Active MQ from 5.5 to 5.7. My producer application sent a message
> t
