activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakub Korab (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-5349) Master broker stays up without access to lease-database-locker
Date Tue, 09 Sep 2014 13:49:29 GMT

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

Jakub Korab updated AMQ-5349:
-----------------------------
    Summary: Master broker stays up without access to lease-database-locker  (was: Master
broker stays without access to lease-database-locker)

> Master broker stays up without access to lease-database-locker
> --------------------------------------------------------------
>
>                 Key: AMQ-5349
>                 URL: https://issues.apache.org/jira/browse/AMQ-5349
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.9.0
>         Environment: RHEL 5.10, Oracle 10
>            Reporter: Jakub Korab
>
> I have a master-slave setup running using a basic lease-database-locker config against
an Oracle database.
> <persistenceAdapter>
>     <jdbcPersistenceAdapter dataDirectory="activemq-data" dataSource="#oracle-ds"
lockKeepAlivePeriod="5000">
>         <locker>
>             <lease-database-locker lockAcquireSleepInterval="10000"/>
>         </locker>
>     </jdbcPersistenceAdapter>
> </persistenceAdapter>
> When the network connection to the database is dropped, the master stays up, accepting
messages (and throwing JMS exceptions). This  effect is that a slave is able to become a master
in the meantime, without the clients failing over to it.
> The broker should cease being the master if it cannot reach the database to extend its
lease.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message