activemq-dev mailing list archives

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

             Summary: Master broker stays without access to lease-database-locker
                 Key: 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.

    <jdbcPersistenceAdapter dataDirectory="activemq-data" dataSource="#oracle-ds" lockKeepAlivePeriod="5000">
            <lease-database-locker lockAcquireSleepInterval="10000"/>

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

View raw message