Summary

Server upgrades from Moka5 4.0 to Moka5 4.1 fail if ActiveMQ is enabled. This article describes the issue, planned resolution, and a workaround.

Applies To

All Moka5 installations with ActiveMQ enabled

Description

Server upgrades from Moka5 4.0 to Moka5 4.1 fail if ActiveMQ is enabled. In some cases, the upgrade will complete successfully, but Moka5 will fail to launch.

ActiveMQ is a deprecated feature that allowed administrators to monitor traffic on server ports. Support for ActiveMQ was dropped in 2011, but the feature may still be set to enabled on Moka5 servers.

Planned Resolution

Future versions of the Moka5 server installer will detect if ActiveMQ is enabled and prompt the administrator to disable it before proceeding with the installation.

Workaround

Disable ActiveMQ before you upgrade to Moka5 4.1. To disable the ActiveMQ service edit the m5es.properties file in the management server’s conf folder and remove the m5es.activemqEnabled property.

1. Navigate to the Management Server's "conf" directory.
2. Open the m5es.properties file.
3. Determine whether ActiveMQ is enabled.
   
   If ActiveMQ services are activated, the m5es.properties will show that
   m5es.activemqEnabled=true
   
   Example: An m5es.properties file with ActiveMQ enabled.
   
   m5es.activemqEnabled=true
   m5es.derbyEnabled=true
   m5es.port=8005
   m5es.opendsEnabled=true
   m5es.address=localhost
   m5es.uuid=ea22697e-2abb-48de-ab8e-cf0e76c7500e
   m5es.tomcatEnabled=true
   
   If the following line appears in the m5es.properties file:
   
   m5es.activemqEnabled=false
   
   or if no line referencing ActiveMQ appears in the file, ActiveMQ is already disabled. No changes are necessary.
   
4. If ActiveMQ is enabled, delete the m5es.activemqEnabled property from the m5es.properties file, then save your changes.
   
   Example: An m5es.properties file with the ActiveMQ property removed.
   
   m5es.port=8005
   m5es.opendsEnabled=true
   m5es.address=localhost
   m5es.uuid=ea22697e-2abb-48de-ab8e-cf0e76c7500e
   m5es.tomcatEnabled=true