You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dmitry Tsigelnik (JIRA)" <ji...@apache.org> on 2008/06/20 11:39:00 UTC

[jira] Created: (AMQ-1813) shutdownOnMasterFailure="true" is ignored when broker starting

shutdownOnMasterFailure="true" is ignored when broker starting
--------------------------------------------------------------

                 Key: AMQ-1813
                 URL: https://issues.apache.org/activemq/browse/AMQ-1813
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.1.0
            Reporter: Dmitry Tsigelnik


If slave broker cannot connect to master when slave broker starting, slave broker doesn't stop starting and starts all connectors
I think it's a bad behavior. It must shutdown when shutdownOnMasterFailure="true" 

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


[jira] Resolved: (AMQ-1813) shutdownOnMasterFailure="true" is ignored when broker starting

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies resolved AMQ-1813.
-----------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 5.4.0)
                   5.3.0

Fixed by SVN revision 813980

> shutdownOnMasterFailure="true" is ignored when broker starting
> --------------------------------------------------------------
>
>                 Key: AMQ-1813
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1813
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Dima
>            Assignee: Rob Davies
>             Fix For: 5.3.0
>
>
> If slave broker cannot connect to master when slave broker starting, slave broker doesn't stop starting and starts all connectors
> I think it's a bad behavior. It must shutdown when shutdownOnMasterFailure="true" 

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


[jira] Commented: (AMQ-1813) shutdownOnMasterFailure="true" is ignored when broker starting

Posted by "Dima (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44306#action_44306 ] 

Dima commented on AMQ-1813:
---------------------------

2ying 

Your logic behaviour is result of race condition. Broker is already started when limit of maxReconnectAttempts=3 is exceeded

> shutdownOnMasterFailure="true" is ignored when broker starting
> --------------------------------------------------------------
>
>                 Key: AMQ-1813
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1813
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Dima
>
> If slave broker cannot connect to master when slave broker starting, slave broker doesn't stop starting and starts all connectors
> I think it's a bad behavior. It must shutdown when shutdownOnMasterFailure="true" 

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


[jira] Assigned: (AMQ-1813) shutdownOnMasterFailure="true" is ignored when broker starting

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies reassigned AMQ-1813:
-------------------------------

    Assignee: Rob Davies

> shutdownOnMasterFailure="true" is ignored when broker starting
> --------------------------------------------------------------
>
>                 Key: AMQ-1813
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1813
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Dima
>            Assignee: Rob Davies
>             Fix For: 5.3.0
>
>
> If slave broker cannot connect to master when slave broker starting, slave broker doesn't stop starting and starts all connectors
> I think it's a bad behavior. It must shutdown when shutdownOnMasterFailure="true" 

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


[jira] Commented: (AMQ-1813) shutdownOnMasterFailure="true" is ignored when broker starting

Posted by "ying (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44305#action_44305 ] 

ying commented on AMQ-1813:
---------------------------

using tcp://master:61616 for masterConnectorURI and shutdownOnMasterFailure="true" , I got the same result.  I think this needs to be fixed too.

but using failover://(tcp://master:61616)?maxReconnectAttempts=3 as the masterConnectorURI , after 3 failed attemp, it will shut down the slave. so shutdownOnMasterFailure is not ignored in the failover protocol case.

> shutdownOnMasterFailure="true" is ignored when broker starting
> --------------------------------------------------------------
>
>                 Key: AMQ-1813
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1813
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Dima
>
> If slave broker cannot connect to master when slave broker starting, slave broker doesn't stop starting and starts all connectors
> I think it's a bad behavior. It must shutdown when shutdownOnMasterFailure="true" 

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