You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Peter Berkman (JIRA)" <ji...@apache.org> on 2017/10/24 19:18:01 UTC
[jira] [Created] (KARAF-5441) ActiveMQ configured for JDBC
Master/Slave prevents all slaves from shutting down
Peter Berkman created KARAF-5441:
------------------------------------
Summary: ActiveMQ configured for JDBC Master/Slave prevents all slaves from shutting down
Key: KARAF-5441
URL: https://issues.apache.org/jira/browse/KARAF-5441
Project: Karaf
Issue Type: Bug
Affects Versions: 4.1.1
Environment: Windows and/or Linux
Reporter: Peter Berkman
I have three karaf nodes running activemq and camel. Activemq is configured for JDBC Master/Slave on all three nodes.
scenario:
node1a is the AMQ Master and node1b and node2a are slaves. Everything working great until you try and shutdown node1b or node2a.
When the shutdown is triggered, the activemq-osgi bundle stays in a "stopping" state until it can obtain the master, then continues to shutdown - ex: forever.
Attached are the activemq.xml configuration files for the three nodes.
I triggered a shutdown on node1b and here is the status of activemq:
{code}
113 | Active | 50 | 5.13.3 | activemq-karaf
152 | Stopping | 50 | 5.13.3 | activemq-osgi
368 | Resolved | 50 | 5.13.3 | activemq-camel
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)