You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dmitry Tsigelnik (JIRA)" <ji...@apache.org> on 2008/06/16 14:55:00 UTC
[jira] Issue Comment Edited: (AMQ-1800) Redilivery counter increase
incredible
[ https://issues.apache.org/activemq/browse/AMQ-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43481#action_43481 ]
tsigelnik edited comment on AMQ-1800 at 6/16/08 5:53 AM:
----------------------------------------------------------------
I'm sorry
I've ment "I have some transacted sessions"
was (Author: tsigelnik):
I'm sorry
I've mean "I have some transacted sessions"
> Redilivery counter increase incredible
> --------------------------------------
>
> Key: AMQ-1800
> URL: https://issues.apache.org/activemq/browse/AMQ-1800
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.1.0
> Reporter: Dmitry Tsigelnik
>
> I have some transacted session. Each session has one consumer which recive messages in parallel from one queue.
> Also I use redeliveryPolicy. When I restart my application and close connection which close sessions which close consumers, message jumps from one closing consumer to another while all consumers will be stopped and rediliveryCounter++ executes every time when message is redispatched
> You have to add any flag to connection which says: if connection.stop() is executed then forbore any message redispatching
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.