You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2012/09/28 19:37:07 UTC

[jira] [Created] (APLO-265) Apollo services should more gracefully recover from transient failures.

Hiram Chirino created APLO-265:
----------------------------------

             Summary: Apollo services should more gracefully recover from transient failures. 
                 Key: APLO-265
                 URL: https://issues.apache.org/jira/browse/APLO-265
             Project: ActiveMQ Apollo
          Issue Type: Bug
            Reporter: Hiram Chirino


Sometimes services have errors starting up.  Like when ports are bound by another process.  In these case it seems Apollo fails to start up and remains in the starting state for that service.  Worse yet, it stays suck in that state and cannot be gracefully shutdown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (APLO-265) Apollo services should more gracefully recover from transient failures.

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-265:
-------------------------------

    Component/s: apollo-broker
    
> Apollo services should more gracefully recover from transient failures. 
> ------------------------------------------------------------------------
>
>                 Key: APLO-265
>                 URL: https://issues.apache.org/jira/browse/APLO-265
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>            Reporter: Hiram Chirino
>             Fix For: 1.6
>
>
> Sometimes services have errors starting up.  Like when ports are bound by another process.  In these case it seems Apollo fails to start up and remains in the starting state for that service.  Worse yet, it stays suck in that state and cannot be gracefully shutdown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (APLO-265) Apollo services should more gracefully recover from transient failures.

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-265:
-------------------------------

    Fix Version/s: 1.6
    
> Apollo services should more gracefully recover from transient failures. 
> ------------------------------------------------------------------------
>
>                 Key: APLO-265
>                 URL: https://issues.apache.org/jira/browse/APLO-265
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>            Reporter: Hiram Chirino
>             Fix For: 1.6
>
>
> Sometimes services have errors starting up.  Like when ports are bound by another process.  In these case it seems Apollo fails to start up and remains in the starting state for that service.  Worse yet, it stays suck in that state and cannot be gracefully shutdown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira