You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Rob Waite (JIRA)" <ji...@apache.org> on 2013/02/07 01:02:12 UTC

[jira] [Created] (AMQNET-410) jms.redeliveryPolicy.nonBlockingRedelivery=true not honored by NMS.ActiveMQ

Rob Waite created AMQNET-410:
--------------------------------

             Summary: jms.redeliveryPolicy.nonBlockingRedelivery=true not honored by NMS.ActiveMQ
                 Key: AMQNET-410
                 URL: https://issues.apache.org/jira/browse/AMQNET-410
             Project: ActiveMQ .Net
          Issue Type: New Feature
          Components: ActiveMQ
    Affects Versions: 1.5.6
         Environment: Any
            Reporter: Rob Waite
            Assignee: Jim Gomes
            Priority: Minor


Our system relies on redelivery. We realized that redelivery was performed by the client when we saw consumers appear to slow down or get stuck.

With ActiveMQ 5.6.0, jms.redeliveryPolicy.nonBlockingRedelivery was added to allow the client side redelivery to move forward instead of fully handling a particular message's redelivery before moving to other messages.

We realized that it was not implemented in NMS and ended up upgrading to ActiveMQ 5.7.0 which supports server-side redelivery using the Scheduler.

Seems fairly minor and may take a larger effort to implement this, judging from what it would likely do.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira