[
https://issues.apache.org/jira/browse/AMQNET-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Gynnild updated AMQNET-351:
---------------------------------
Description:
See attached unit test.
Test does this:
1) Creates a connection, session and producer (using failover protocol).
2) Creates a connection, session and consumer (using failover protocol).
3) Stops message bus, and starts it again.
4) Sends message.
5) Message is never received. (PROBLEM).
So after a failover messages can be sent successfully, but fails to be received.
Is there an easy workaround for it, as the above breaks the failover scenario?
was:
See attached unit test.
> After failover, messages are sent, but not received
> ---------------------------------------------------
>
> Key: AMQNET-351
> URL: https://issues.apache.org/jira/browse/AMQNET-351
> Project: ActiveMQ .Net
> Issue Type: Bug
> Affects Versions: 1.5.2
> Environment: ActiveMQ NMS 1.5.2 + ActiveMQ 5.5 broker
> Reporter: Frank Gynnild
> Assignee: Jim Gomes
> Priority: Critical
> Attachments: NmsFailoverReceiveTest.cs
>
>
> See attached unit test.
> Test does this:
> 1) Creates a connection, session and producer (using failover protocol).
> 2) Creates a connection, session and consumer (using failover protocol).
> 3) Stops message bus, and starts it again.
> 4) Sends message.
> 5) Message is never received. (PROBLEM).
> So after a failover messages can be sent successfully, but fails to be
> received.
> Is there an easy workaround for it, as the above breaks the failover scenario?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
