You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Kevin Quick (JIRA)" <ji...@apache.org> on 2011/01/25 20:12:43 UTC

[jira] Created: (AMQCPP-349) broker restarts undetectable via tcp: transport

broker restarts undetectable via tcp: transport
-----------------------------------------------

                 Key: AMQCPP-349
                 URL: https://issues.apache.org/jira/browse/AMQCPP-349
             Project: ActiveMQ C++ Client
          Issue Type: Bug
    Affects Versions: 3.2.4
            Reporter: Kevin Quick
            Assignee: Timothy Bish


A client connected to a queue on a broker via a tcp: transport connection receives no indication of a broker restart.

This leaves the client waiting forever for messages on the queue but the broker does not have a subscription for that client.  The client has no indication that it must initiate a reconnection with the broker.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQCPP-349) broker restarts undetectable via tcp: transport

Posted by "Kevin Quick (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AMQCPP-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986633#action_12986633 ] 

Kevin Quick commented on AMQCPP-349:
------------------------------------

Yes.  The receive() method is being called on a Consumer.  The Consumer was created for the original broker instance.  The receive() is being called with a 1.5 second timeout (to allow periodic local processing).  When the original broker is stopped, there does not appear to be any interruption of the current receive() call, and all subsequent receive() calls return normally (with a timeout after their 1.5 second period) as well with a null Message pointer.  It's unclear how many (if any) receive calls were made while the broker was down, but at no point during the broker restart is there any perturbation or variation in the 1.5-second receive() operations.

> broker restarts undetectable via tcp: transport
> -----------------------------------------------
>
>                 Key: AMQCPP-349
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-349
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 3.2.4
>            Reporter: Kevin Quick
>            Assignee: Timothy Bish
>
> A client connected to a queue on a broker via a tcp: transport connection receives no indication of a broker restart.
> This leaves the client waiting forever for messages on the queue but the broker does not have a subscription for that client.  The client has no indication that it must initiate a reconnection with the broker.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AMQCPP-349) broker restarts undetectable via tcp: transport

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/AMQCPP-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986625#action_12986625 ] 

Timothy Bish commented on AMQCPP-349:
-------------------------------------

Are you talking about a consumer performing a receive operation at the time of the connection loss, or some other use case?

> broker restarts undetectable via tcp: transport
> -----------------------------------------------
>
>                 Key: AMQCPP-349
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-349
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 3.2.4
>            Reporter: Kevin Quick
>            Assignee: Timothy Bish
>
> A client connected to a queue on a broker via a tcp: transport connection receives no indication of a broker restart.
> This leaves the client waiting forever for messages on the queue but the broker does not have a subscription for that client.  The client has no indication that it must initiate a reconnection with the broker.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (AMQCPP-349) broker restarts undetectable via tcp: transport

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/AMQCPP-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQCPP-349.
-------------------------------

    Resolution: Fixed

This issue is fixed in trunk and will be part of the v3.3.0 release.

> broker restarts undetectable via tcp: transport
> -----------------------------------------------
>
>                 Key: AMQCPP-349
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-349
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 3.2.4
>            Reporter: Kevin Quick
>            Assignee: Timothy Bish
>
> A client connected to a queue on a broker via a tcp: transport connection receives no indication of a broker restart.
> This leaves the client waiting forever for messages on the queue but the broker does not have a subscription for that client.  The client has no indication that it must initiate a reconnection with the broker.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.