activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQNET-243) failover causes duplicate messages
Date Mon, 15 Mar 2010 17:45:45 GMT


Timothy Bish commented on AMQNET-243:

I'd recommend testing this against the official 1.2.0 release as that's been out for quite
some time now.

> failover causes duplicate messages
> ----------------------------------
>                 Key: AMQNET-243
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.1.0
>            Reporter: Mark Gellings
>            Assignee: Jim Gomes
> Reference for specifics on problem.
> Attached to that issue is a zip file which is password protected with password "fridaytest".
> We're using ActiveMQ v5.2, jdbc master/slave MSSQL 2008. Attached is an NMS v1.2 RC4
consumer with a transacted session as well as activemq.xml.
> To replicate:
> 1) Work through the console prompts and produce 50 msgs.
> 2) Restart console and start consuming those 50 msgs.
> 3) In the middle of the consumer processing, restart broker
> 4) The last message consumer was processing will be resent and not marked as redelivered.
(this is the idempotent msg problem. Ex. - instead of $500 getting deposited into your account,
$1000 does)
> 5) Then NMS blows up which seems like a different problem?
> From what I understand this shouldn't be the case if you use a transacted session, however
the attached console app can prove it is a problem.
> Bottomline--I thought this was why the camel idempotent consumer pattern [1] existed
which can be leveraged by java clients.
> [1]
> Regards,
> Mark

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message