activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Gynnild (JIRA)" <>
Subject [jira] [Commented] (AMQNET-341) After failover happens, messages are no longer delivered
Date Mon, 05 Sep 2011 09:03:09 GMT


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:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>         Environment: Version: 1.5.1 ( 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
> 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:


View raw message