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

Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2009/09/11 13:34:14 UTC

[jira] Created: (AMQ-2387) Add a passive master/slave option - so that a slave can detect a master has died - but no messages are replicated

Add a passive master/slave option - so that a slave can detect a master has died - but no messages are replicated
-----------------------------------------------------------------------------------------------------------------

                 Key: AMQ-2387
                 URL: https://issues.apache.org/activemq/browse/AMQ-2387
             Project: ActiveMQ
          Issue Type: New Feature
    Affects Versions: 5.2.0, 5.1.0, 5.0.0
            Reporter: Rob Davies
            Assignee: Rob Davies
             Fix For: 5.3.0


This requirement comes from using replicated databases - where you may wish a slave to only start on the replica db (which may be on another machine) - but ActiveMQ does not replicate the state - that's done by the database. - see http://stackoverflow.com/questions/1062723/activemq-service-failover-and-database-failover

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

[jira] Resolved: (AMQ-2387) Add a passive master/slave option - so that a slave can detect a master has died - but no messages are replicated

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.

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

Rob Davies resolved AMQ-2387.
-----------------------------

    Resolution: Fixed

Fixed by SVN revision 813906

> Add a passive master/slave option - so that a slave can detect a master has died - but no messages are replicated
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2387
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2387
>             Project: ActiveMQ
>          Issue Type: New Feature
>    Affects Versions: 5.0.0, 5.1.0, 5.2.0
>            Reporter: Rob Davies
>            Assignee: Rob Davies
>             Fix For: 5.3.0
>
>
> This requirement comes from using replicated databases - where you may wish a slave to only start on the replica db (which may be on another machine) - but ActiveMQ does not replicate the state - that's done by the database. - see http://stackoverflow.com/questions/1062723/activemq-service-failover-and-database-failover

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