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 <badri_na...@yahoo.com> wrote:

> 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 messages
> I see a URL:
> failover:(tcp://host:port?soWriteTimeout=500)?jms.useAsyncSend=true&trackMessages=true
> 
> 2) Will adding trackMessages=true in the URL on the consumer side help not
> sending dupe messages?
> 
> 3) In the consumer program's onMessage method: 
> 
> public void onMessage(javax.jms.Message message, javax.jms.Session session)
> {
>            tId = message.getStringProperty("TID");
>            name = message.getStringProperty("NAME");
>            processMessage(message, session, tId, name);
> }
> 
> Will adding session.commit() before tId=message.getStringProperty("TID")
> help in anyway?
> 
> Thanks.
> 
> 
> 
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/Duplicate-messages-sent-in-Active-MQ-5-7-tp4675063p4675207.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to