[
https://issues.apache.org/activemq/browse/AMQNET-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58276#action_58276
]
Mark Gellings commented on AMQNET-243:
--------------------------------------
Problem is we need it to not happen at all. When processing idempotent
messages they cannot be processed twice. So I don't think duplicating the java
code would fix this.
> failover causes duplicate messages
> ----------------------------------
>
> Key: AMQNET-243
> URL: https://issues.apache.org/activemq/browse/AMQNET-243
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: NMS
> Affects Versions: 1.1.0
> Reporter: Mark Gellings
> Assignee: Jim Gomes
>
> Reference https://issues.apache.org/activemq/browse/AMQ-2627 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] http://fusesource.com/docs/router/1.6/eip/MsgEnd-Idempotent.html
> Regards,
> Mark
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
