Stop script in fuse activemq does not stop the slave node when failover deployments setup is done.

Solution Unverified - Updated -

Issue

  • When we configure failover deployment with JDBC master slave. In this setup the ./stop script does not stop the slave instance .
    stop script fails with Can't connect to the container. The container is not running

  • We run Fuse 6.1 pair on two machines in Karaf failover configuration with JDBC lock on an Oracle DB as described here:

    https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html-single/Configuring_and_Running_Red_Hat_JBoss_Fuse/#ESBRuntimeFailoverJdbc

    The Fuse 6.1 instance that is currently the slave cannot be stopped as usual by invoking bin/stop. stop script says:
    Can't connect to the container. The container is not running.

    We either need to login and type the command "shutdown" then enter "yes" or kill the proccess. Both methods are not very "operations-friendly".

    Is there a way to make the stop script work with the slave instance?

  • We have an A-MQ 6.1 master/slave setup on MS Windows ( following chapter 3 of
    https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_A-MQ/6.1/pdf/Fault_Tolerant_Messaging/Red_Hat_JBoss_A-MQ-6.1-Fault_Tolerant_Messaging-en-US.pdf )

    A-MQ are started/stopped as Windows Services
    Trying to stop the slave node takes more than 3 minutes (looks like the The SimpleFileLock thread does not get stopped immediately, but continues to poll the kahaDB for the availability of lock)
    The master node always stops nicely without delay.
    Is there a way to fix that?

Environment

  • Red Hat JBoss Fuse
    • 6.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.