activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [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
Date Fri, 11 Sep 2009 16:17:14 GMT

     [ 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.


Mime
View raw message