[
https://issues.apache.org/jira/browse/AMQNET-589?focusedWorklogId=276540&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-276540
]
ASF GitHub Bot logged work on AMQNET-589:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Jul/19 07:53
Start Date: 15/Jul/19 07:53
Worklog Time Spent: 10m
Work Description: HavretGC commented on issue #4: AMQNET-589: Failover
implementation
URL: https://github.com/apache/activemq-nms-amqp/pull/4#issuecomment-511305350
It's really strange because it works for me just fine. I am using Windows 10
Box with Apache ActiveMQ Artemis 2.8.1 broker.
Here's the trace log from HelloWorld netcore2.2 and net462 runs:
```
scheme: amqp
Creating Connection...
Created Connection.
Version: NMS AMQP Version: [
NMSVersion = 1.8,
NMSProviderName = Apache.NMS.AMQP,
Provider AssemblyVersion = 1.0.0.0,
Provider AssemblyFileVersion = 1.0.0.0,
Provider AssemblyInformationalVersion = 1.0.0,
Provider AMQP Assembly Name = Amqp.Net,
Provider AMQP Assembly Version = 2.1.0.0
]
Creating Session...
Session Created.
Creating Message Producer for : Apache.NMS.AMQP.NmsQueue...
Created Message Producer.
Sending Msg: NmsTextMessage { Hello World! }
Starting Connection...
Connection Started: True Resquest Timeout: -00:00:00.0010000
Sending 1 Messages...
Received Message with id ID:0 and contents NmsTextMessage { Hello World! n:
0 }.
Closing Connection...
Warn: Exception: , Description = Internal Error.
Connection Closed.
Process finished with exit code 0.
```
The same thing for StructuredMessage:
```
scheme: amqp
Creating Connection...
Created Connection.
Version: NMS AMQP Version: [
NMSVersion = 1.8,
NMSProviderName = Apache.NMS.AMQP,
Provider AssemblyVersion = 1.0.0.0,
Provider AssemblyFileVersion = 1.0.0.0,
Provider AssemblyInformationalVersion = 1.0.0,
Provider AMQP Assembly Name = Amqp.Net,
Provider AMQP Assembly Version = 2.1.0.0
]
Creating Session...
Session Created.
Creating Message Producer for : Apache.NMS.AMQP.NmsQueue...
Created Message Producer.
Starting Connection...
Connection Started: True Resquest Timeout: -00:00:00.0010000
Sending Msg: NmsMapMessage {
Apache.NMS.AMQP.Provider.Amqp.Message.AmqpNmsMapMessageFacade }
Sending Msg: NmsStreamMessage {
Apache.NMS.AMQP.Provider.Amqp.Message.AmqpNmsStreamMessageFacade }
Received Message with id ID:0 and contents NmsMapMessage {
Apache.NMS.AMQP.Provider.Amqp.Message.AmqpNmsMapMessageFacade }.
Received Message with id ID:1 and contents NmsStreamMessage {
Apache.NMS.AMQP.Provider.Amqp.Message.AmqpNmsStreamMessageFacade }.
Message contains Property[foobar] = 42
Closing Connection...
Warn: Exception: , Description = Internal Error.
Connection Closed.
```
The only problem I see here (apart from from the blunder with adding the
same key to annotation map) is the fact that the clean connection close is
sending the exception as the same callback is being invoked whether or not the
connection close was clean.
----------------------------------------------------------------
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: 276540)
Time Spent: 7h 10m (was: 7h)
> 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 10m
> 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)
