[prev in list] [next in list] [prev in thread] [next in thread]
List: activemq-dev
Subject: [jira] [Closed] (AMQNET-461) FailoverTransport PoisonAcks Rollbacked messages
From: "Timothy Bish (JIRA)" <jira+amqnet () apache ! org>
Date: 2014-08-28 19:45:11
Message-ID: JIRA.12679201.1384430448655.2896.1409255111015 () arcas
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/AMQNET-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]
Timothy Bish closed AMQNET-461.
-------------------------------
Resolution: Cannot Reproduce
Assignee: Timothy Bish (was: Jim Gomes)
Attempted to reproduce with all the latest fixes but could not. If a test case can \
be provided we can reopen and investigate.
> FailoverTransport PoisonAcks Rollbacked messages
> ------------------------------------------------
>
> Key: AMQNET-461
> URL: https://issues.apache.org/jira/browse/AMQNET-461
> Project: ActiveMQ .Net
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Remo Gloor
> Assignee: Timothy Bish
>
> When using FailoverTransport with nonBlockingRedelivery messages get PoisonAcked:
> 1. Message is rolledback e.g. due to a concurrency exception on the db or any other \
> processing error. 2. Message is sheduled for redelivery e.g. in 30 Sec.
> 3. Connection is lost before message is redelivered
> 4. Connection is reestablished before message is redelivered.
> 5. Server redelivers message due to the connection loss
> 6. Message is dsipatched and processed.
> 7. Resheduled Message gets dispatched => Duplicate
> 8. No previously delivered messages => Send PoisonAck => Message is in the DLQ even \
> though it is processed succesfully.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic