[
https://issues.apache.org/activemq/browse/AMQNET-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46809#action_46809
]
Allan Schrum commented on AMQNET-26:
------------------------------------
Eureka! The basics seem to work. I can connect using a failover transport and
hold a conversation. Basically I can repeat with a failover transport the same
functions I can do with a tcp transport. All the actual failover logic
(reconnect, resend of messages, etc.) are untested. That is for tomorrow.
Although I did a quick reconnect test and it worked fine! Using TcpView I
closed the connection and the client reestablished it with no application-level
impact.
Testing will require some assistance. There are many operating modes that need
to be verified.
I shall construct patches and submit them tomorrow AM for your review. These
can be applied to the latest(?) version 707373 (and most likely HEAD if it has
changed).
-Allan
> Add failover:// to NMS client
> -----------------------------
>
> Key: AMQNET-26
> URL: https://issues.apache.org/activemq/browse/AMQNET-26
> Project: ActiveMQ .Net
> Issue Type: New Feature
> Components: ActiveMQ Client
> Reporter: Denis Abramov
> Assignee: Jim Gomes
> Priority: Critical
> Fix For: 1.1
>
> Attachments: Apache.NMS.707373.diff, Apache.NMS.ActiveMQ.707373.diff,
> FailoverPatch.diff
>
>
> Please add failover:// to C# NMS Client. I would add it but I don't know how
> to resume a stream once it is broken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
