Problem Note 54802: ActiveMQ JMS Broker services fails to start on a slave machine when it is clustered and running on two different machines
In SAS® 9.4, ActiveMQ JMS Broker services fails to start on a slave machine when it is clustered and running on two different machines (that is, in a master/slave configuration). When this problem happens, the following message appears in the activemq.log file during services startup:
2014-09-30 11:55:48,886 | INFO | Database /opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock is locked... waiting 10 seconds for the database to be unlocked. Reason: java.io.IOException: File '/opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock' could not be locked. | org.apache.activemq.store.SharedFileLocker | main
2014-09-30 11:55:58,887 | INFO | Database /opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock is locked... waiting 10 seconds for the database to be unlocked. Reason: java.io.IOException: File /opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock' could not be locked. | org.apache.activemq.store.SharedFileLocker | main
2014-09-30 11:56:08,888 | INFO | Database /opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock is locked... waiting 10 seconds for the database to be unlocked. Reason: java.io.IOException: File /opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock' could not be locked. | org.apache.activemq.store.SharedFileLocker | main
2014-09-30 11:56:18,890 | INFO | Database /opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock is locked... waiting 10 seconds for the database to be unlocked. Reason: java.io.IOException: File /opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock' could not be locked. | org.apache.activemq.store.SharedFileLocker | main
2014-09-30 11:56:28,892 | INFO | Database /opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock is locked... waiting 10 seconds for the database to be unlocked. Reason: java.io.IOException: File /opt/sasconfig/9.4/midtier/active_mq_data/kahadb/lock' could not be locked. | org.apache.activemq.store.SharedFileLocker | main
To solve this problem, follow these steps on the middle-tier machine:
- Modify the brokerUrl="failover:. . ." properties definition in the server.xml file that resides in SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer1_1\conf\ so that it points to the relevant host name and port number for both the master machine and the slave machine:
xaProperties.brokerURL="failover:(tcp://host-name-of-master-machine:port,tcp://host-name-of-slave-machine:port)?randomize=false"/>
- Restart the SAS 9.4 ActiveMQ JMS Broker services on both of the machines. Check the activemq.log file on both the machines to ensure that the services start properly.
- Restart all of the SASServer instances (SASServer1_1, SASServerN_1, and so on).
Operating System and Release Information
| SAS System | SAS JMS Broker | Linux for x64 | 9.4 | | 9.4 TS1M2 | |
| Microsoft Windows Server 2012 R2 Std | 9.4 | | 9.4 TS1M2 | |
| Solaris for x64 | 9.4 | | 9.4 TS1M2 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2014-12-10 09:26:55 |
| Date Created: | 2014-12-08 14:21:20 |
