[
https://issues.apache.org/jira/browse/AMQNET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097064#comment-13097064
]
Frank Gynnild commented on AMQNET-341:
--------------------------------------
There's a workaround to the above problem: Using "ReceiveCommandNoWait" works
after connection has been resumed from the failover situation.
> After failover happens, messages are no longer delivered
> --------------------------------------------------------
>
> Key: AMQNET-341
> URL: https://issues.apache.org/jira/browse/AMQNET-341
> Project: ActiveMQ .Net
> Issue Type: Bug
> Environment: Version: 1.5.1 (1.5.1.2341) of Apache NMS for ActiveMQ
> Class Library
> Windows 2008 R2
> .NET 4.0
> Reporter: Frank Gynnild
> Assignee: Jim Gomes
> Priority: Critical
> Attachments: Stacktrace.jpg
>
>
> I've some NMS clients (4 in total) that uses synchronized receiving (non
> message listener based),
> that all are try to receive to the same queue using message selectors.
> When failover occurs (can be tested with stopping and starting the message
> bus), I get the interrupt and the resumed
> events, but the clients block for ever trying to receive the next message.
> The messages can be seen
> in the ActiveMQ Web Console. I have even tried using a time-out and try to
> receive again, but they are stuck until
> I restart the process.
> Is this a known issue?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
