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

Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <qp...@incubator.apache.org> on 2008/11/24 20:01:44 UTC

[jira] Created: (QPID-1484) qpid-printevents needs to be manually restarted each time a broker connection is lost

qpid-printevents needs to be manually restarted each time a broker connection is lost
-------------------------------------------------------------------------------------

                 Key: QPID-1484
                 URL: https://issues.apache.org/jira/browse/QPID-1484
             Project: Qpid
          Issue Type: Bug
          Components: Qpid Managment Framework
    Affects Versions: M4
            Reporter: Ted Ross
            Assignee: Ted Ross
             Fix For: M4


The qpid-printevents CLI utility doesn't properly handle connection loss and needs to be restarted whenever the broker(s) it is watching restart or the connections to the brokers are lost.


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

[jira] Resolved: (QPID-1484) qpid-printevents needs to be manually restarted each time a broker connection is lost

Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.

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

Ted Ross resolved QPID-1484.
----------------------------

    Resolution: Fixed

> qpid-printevents needs to be manually restarted each time a broker connection is lost
> -------------------------------------------------------------------------------------
>
>                 Key: QPID-1484
>                 URL: https://issues.apache.org/jira/browse/QPID-1484
>             Project: Qpid
>          Issue Type: Bug
>          Components: Qpid Managment Framework
>    Affects Versions: M4
>            Reporter: Ted Ross
>            Assignee: Ted Ross
>             Fix For: M4
>
>
> The qpid-printevents CLI utility doesn't properly handle connection loss and needs to be restarted whenever the broker(s) it is watching restart or the connections to the brokers are lost.

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