You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Frank Gynnild (JIRA)" <ji...@apache.org> on 2011/09/02 13:14:09 UTC
[jira] [Created] (AMQNET-341) After failover happens, messages are
no longer delivered
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
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
[jira] [Issue Comment Edited] (AMQNET-341) After failover happens,
messages are no longer delivered
Posted by "Frank Gynnild (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097064#comment-13097064 ]
Frank Gynnild edited comment on AMQNET-341 at 9/5/11 9:03 AM:
--------------------------------------------------------------
There's a workaround to the above problem: Using ReceiveNoWait() works after connection has been resumed from the failover situation.
was (Author: fgynnild):
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
[jira] [Commented] (AMQNET-341) After failover happens, messages
are no longer delivered
Posted by "Frank Gynnild (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095928#comment-13095928 ]
Frank Gynnild commented on AMQNET-341:
--------------------------------------
When this happens, it seems to completely ignore the time-out while waiting to receive the command, so it's blocking on that statement.
> 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
>
> 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
[jira] [Resolved] (AMQNET-341) After failover happens, messages are
no longer delivered
Posted by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-341.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
1.5.3
This should be fixed now
> 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
> Fix For: 1.5.3, 1.6.0
>
> 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.
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
[jira] [Commented] (AMQNET-341) After failover happens, messages
are no longer delivered
Posted by "Frank Gynnild (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AMQNET-341) After failover happens, messages
are no longer delivered
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147695#comment-13147695 ]
Timothy Bish commented on AMQNET-341:
-------------------------------------
We need a test case in order to investigate this. Need to see what Uri the client uses etc.
> 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.
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
[jira] [Updated] (AMQNET-341) After failover happens, messages are
no longer delivered
Posted by "Frank Gynnild (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Gynnild updated AMQNET-341:
---------------------------------
Attachment: Stacktrace.jpg
> 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