activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allan Schrum (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-137) Add support for redelivery policy
Date Thu, 05 Feb 2009 20:21:59 GMT

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

Allan Schrum commented on AMQNET-137:
-------------------------------------

Much of the supporting classes were added in support of the failover transport that would
be needed to support this. State tracking, transacations, etc, so adding support for redelivery
should be relatively easy. Failover uses these mechanisms to silently replay messages in the
event of a transport failure. A similar process would be used to redeliver stuff to the client
upon demand or rollback.

Before starting on this process, a clean review of the State (directory) code is in order.

> Add support for redelivery policy
> ---------------------------------
>
>                 Key: AMQNET-137
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-137
>             Project: ActiveMQ .Net
>          Issue Type: New Feature
>          Components: ActiveMQ Client
>    Affects Versions: 1.1
>            Reporter: Mark Keenan
>            Assignee: Jim Gomes
>            Priority: Minor
>             Fix For: 1.2
>
>
> It would be nice if we could set redelivery policy (similar to the Java client).  See
this ActiveMQ mailing list thread for details:
> http://www.nabble.com/configuring-redelivery-with-NMS-td21714808.html#a21717670

-- 
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