You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/11/11 11:08:44 UTC

[jira] Updated: (QPID-1452) ApplicationRegistry does not signal when shutdown has completed.

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

Martin Ritchie updated QPID-1452:
---------------------------------

    Description: 
Summary:
Currently when the ApplicationRegistry is shutdown it only logs that it is starting to shutdown and not when that process is completed. This is particularly annoying when debugging InVM failover cases and we would like to know when the failed broker has finished its shutdown methods.

Proposed Change:

A wrapped info statement at the end of ApplicationRegistry.close() should do the trick.

  was:
Summary:
Currently when the ApplicationRegistry is shutdown it only logs that it is starting to shutdown and not when that process is completed. This is particularly annoying when debugging InVM failover cases and we would like to know when the failed broker has finished its shutdown methods.


> ApplicationRegistry does not signal when shutdown has completed.
> ----------------------------------------------------------------
>
>                 Key: QPID-1452
>                 URL: https://issues.apache.org/jira/browse/QPID-1452
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker, Starter
>    Affects Versions: M4
>            Reporter: Martin Ritchie
>            Priority: Minor
>
> Summary:
> Currently when the ApplicationRegistry is shutdown it only logs that it is starting to shutdown and not when that process is completed. This is particularly annoying when debugging InVM failover cases and we would like to know when the failed broker has finished its shutdown methods.
> Proposed Change:
> A wrapped info statement at the end of ApplicationRegistry.close() should do the trick.

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