You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2009/12/12 00:09:52 UTC

[jira] Closed: (AMQNET-222) Commands.Message RedeliveryCounter not preserved when creating a new message

     [ https://issues.apache.org/activemq/browse/AMQNET-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQNET-222.
-------------------------------

    Resolution: Working as Designed

This as well as the other properties in the Message Commands are OpenWire specific values, and there is no guarantee placed on them to allow for user modification.  When a Message is sent by a producer it is considered to not be a redelivered message, and so the OpenWire property RedeliveryCounter is always set to zero.  NMS 1.1.0 not setting this was an error.  

> Commands.Message RedeliveryCounter not preserved when creating a new message
> ----------------------------------------------------------------------------
>
>                 Key: AMQNET-222
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-222
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.2.0
>         Environment: ActiveMQ 5.2
>            Reporter: Mark Gellings
>            Assignee: Jim Gomes
>             Fix For: 1.2.0
>
>
> In v1.1 when producing a message with the RedeliveryCounter = 4 (for example), the message came through a consumer with that value set to 4.  Now it appears the value is reset to 0.
> Is this an intentional breaking change?

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