[
https://issues.apache.org/jira/browse/AMQNET-589?focusedWorklogId=276790&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-276790
]
ASF GitHub Bot logged work on AMQNET-589:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Jul/19 15:38
Start Date: 15/Jul/19 15:38
Worklog Time Spent: 10m
Work Description: cjwmorgan-sol commented on issue #4: AMQNET-589:
Failover implementation
URL: https://github.com/apache/activemq-nms-amqp/pull/4#issuecomment-511454085
I find I only hit the case when I publish and receive more then 30 messages,
I tried with 50 messages. Also I think the broker I'm using hits the issue in
amqpnetlite https://github.com/Azure/amqpnetlite/issues/351 where sync sends
take 1 sec per message. This makes the first 30 messages expired. Turns out my
broker does not support the modified outcome for deliveries. This causes the
exception to occur since the broker returns an outcome list without the
modified outcome symbol, in the attach response so when the client sends an
modified disposition the broker terminates the link.
Would it be possible to have the AmqpConsumer check the attach response for
support outcomes and do the following:
1. Determine if the list of supported outcomes is sufficient to process
messages. If not fail to create the consumer.
1. For non critical protocol outcomes like modified could the client not
send the outcome disposition on links that do not support the outcome.
----------------------------------------------------------------
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: 276790)
Time Spent: 7h 40m (was: 7.5h)
> 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: 7h 40m
> 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)
