[
https://issues.apache.org/activemq/browse/AMQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45972#action_45972
]
Hiram Chirino commented on AMQ-1952:
------------------------------------
I think we may need to extend the wire protocol a bit to gracefully handle
this. When the consumer closes, it should let the broker know the last message
id that was delivered to the client. That way the broker can mark all the
messages between the last one acked and the last one delivered to the client as
being redelivered and the rest would not get marked as being redelivered.
But even without the wire protocol change, this case should work today if the
prefetch is set to 0.
> JMSXDeliveryCount is not being incremented correctly
> ----------------------------------------------------
>
> Key: AMQ-1952
> URL: https://issues.apache.org/activemq/browse/AMQ-1952
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 5.3.0
>
>
> There seems to be a problem with respect to the Redelivered and
> JMSXDeliveryCount
> properties, in that these properties are being incremented even when the
> message
> has never been re-delivered to the consumer (i.e. on initial message
> delivery).
> The behavior appears to be happening when there is > 1 messages in the queue,
> the second message and subsequent messages show the redelivered property set
> to true and
> JMSXDeliverCount property with a number greater than 1, when those messages
> have not been
> re-delivered before.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
