skip to Main Content

SAS JMS Broker Server is not started on the Linux Server

Background: We’ve installed SAS binaries & configuration on Amazon linux server successfully without getting any error or warning msg. After post install customization, we’ve stopped all SAS servers via sas.servers script and when we try to start sas.servers JMS broker server did not start.

And we’re getting the following warning & error messages:

[sas@abc-sas-a activemq]$ /opt/sas/config/Lev1/Web/activemq/bin/activemq start

INFO: Loading ‘/opt/sas/config/Lev1/Web/activemq/bin/env’

INFO: Using java ‘/opt/sas/sashome/SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java’

INFO: Starting – inspect logfiles specified in logging.properties and log4j.properties to get details

INFO: pidfile created : ‘/opt/sas/config/Lev1/Web/activemq/data/activemq-abc-sas-a.local.com.pid’ (pid ‘5224’)

[sas@abc-sas-a activemq]$ /opt/sas/config/Lev1/Web/activemq/bin/activemq status

INFO: Loading ‘/opt/sas/config/Lev1/Web/activemq/bin/env’

INFO: Using java ‘/opt/sas/sashome/SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java’

ActiveMQ not running

[sas@abc-sas-a activemq]$


Resolution steps:

Run this command

[sas@abc-sas-a ~]$ /opt/sas/config/Lev1/Web/activemq/bin/activemq console

INFO: Loading ‘/opt/sas/config/Lev1/Web/activemq/bin/env’

INFO: Using java ‘/opt/sas/sashome/SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java’

INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C)

INFO: Creating pidfile /opt/sas/config/Lev1/Web/activemq/data/activemq-abc-sas-a.local.com.pid

Error: Password file read access must be restricted: /opt/sas/config/Lev1/Web/activemq/conf/jmx.password

sun.management.AgentConfigurationError

        at sun.management.jmxremote.ConnectorBootstrap.checkPasswordFile(ConnectorBootstrap.java:577)

        at sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(ConnectorBootstrap.java:426)

        at sun.management.Agent.startAgent(Agent.java:262)

        at sun.management.Agent.startAgent(Agent.java:452)

[sas@aais-sas-a ~]$

For resolution we need to set permission 600 for jmx.password file using this command:

chmod 600 /opt/sas/config/Lev1/Web/activemq/conf/jmx.password

Try to run /opt/sas/config/Lev1/Web/activemq/bin/activemq console command again and this time it will start the JMS broker server.

Back To Top