activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-221) Should be able to max out retries on a message and then sent to dead letter queue
Date Fri, 11 Dec 2009 20:27:52 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56401#action_56401
] 

Timothy Bish commented on AMQNET-221:
-------------------------------------

The properties and bodies of received messages are always marked as read-only when they are
received by a client, if the client is going to rebroadcast the message then it can either
call ClearBody if it wants to only alter the body, ClearProperties if it wishes to alter properties
only.  

So in your case you could retrieve the Text of the message and then call ClearBody which will
reset the message bodies state to Read / Write and then set your updated text on the message.

> Should be able to max out retries on a message and then sent to dead letter queue
> ---------------------------------------------------------------------------------
>
>                 Key: AMQNET-221
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-221
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.2.0
>         Environment: ActiveMQ 1.2
>            Reporter: Mark Gellings
>            Assignee: Jim Gomes
>
> Using AcknowledgementMode.ClientAcknowledge, after exhausting all of the retries of a
message the message remains in the original queue.
> With v1.1 message is sent to the DLQ. 

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


Mime
View raw message