[
https://issues.apache.org/jira/browse/AMQNET-589?focusedWorklogId=275550&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-275550
]
ASF GitHub Bot logged work on AMQNET-589:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Jul/19 23:35
Start Date: 11/Jul/19 23:35
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #4: AMQNET-589:
Failover implementation
URL: https://github.com/apache/activemq-nms-amqp/pull/4#issuecomment-510691179
Re behaviour of non persistent sending blocking. This means if a send
failure occurs the sender will not get notification e.g. if queue is not
permissioned. Whilst i see the perf benefit, it would break the contract of the
sender getting an exception if a send is not successful.
The feature could be added later though where a CF setting to block on
persistent, where a user could set it to false for the perf benefit at trade
off of not getting exceptions. But thats an enhancement IMHO.
By default it should be blocking so if send to an address fails due to
security or other confguration reasons the producer throws exception.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 275550)
Time Spent: 0.5h (was: 20m)
> NMS AMQP Failover implementation
> --------------------------------
>
> Key: AMQNET-589
> URL: https://issues.apache.org/jira/browse/AMQNET-589
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ, AMQP, NMS
> Affects Versions: 1.8.0
> Reporter: Krzysztof Porebski
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Implement failover in NMS AMQP the same way as it is implemented in QpidJMS.
> This will involve some major rework, as current design is too rigid to
> introduce this feature.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
