Master/slave brokers do not work correctly
Issue
-
We have two AMQ brokers configured in Master/Slave topology with Database persistence. We are using lease-database-locker in jdbcPersistenceAdabter. So when Master broker is stopped , the Slave takes over successfully. But the problem is when the Slave Broker is stopped, the Master Broker for some reason stop and shutdown.
-
When the Windows Service of a particular broker (e.g. JBossAMQ1) is running on both servers (i.e. one active and one passive), shutting down the Windows Service of the passive broker instance takes a long time complete. As a result the Windows Service Manager action times out and the service remains in "Stopping" state for some time before eventually shutting down. Shutting down the service of the corresponding active broker instance while in "Stopping" state causes the service of the passive instance to immediately transition to "Stopped". Shutdown of the Windows Service of an active broker instance never exhibits this problem.
Environment
- Red Hat JBoss A-MQ 6.X
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
