Subscription messages not being sent - [ActiveMqVendorImpl] Problem creating JMS Connecton : javax.jms.JMSException

Products

• Automic Automation Intelligence

Issue/Introduction

Subscription messages not being sent.

 

jaws.log shows messages like:

WARN [ActiveMqVendorImpl] Problem creating JMS Connecton : javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused (Connection refused) at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)

 

Then the errors below occurred later on which repeated, which looks like cause subscriptions not to be published.

 

 

 

 

Environment

Release : 6.0.2

 

Resolution

It appears the activemq micro service didn't fully shutdown when AAI was brought down.

 

On startup messages like below

ERROR [org.apache.activemq.broker.BrokerService] Failed to start Apache ActiveMQ (termaActiveMQ, ID:ivapp1241842.randolph.ms.com-41956-1636311963774-0:1): java.io.IOException: Transport Connector could not be registered in JMX: java.io.IOException: Failed to bind to server socket: nio://127.0.0.1:61616?maximumConnections=1000&wireFormat.maxFrameSize=1000000000 due to: java.net.BindException: Address already in use

 

Then the errors below occurred later on which repeated, which looks like cause subscriptions not to be published.

 

2021/11/07 14:43:48.080 WARN [ActiveMqVendorImpl] Problem creating JMS Connecton : javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused (Connection refused)
 at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)

 

On the next shutdown you should check to see if something is still running on port 61616 before attempting to start the AAI service.

 

You could use a command like below:

sudo lsof -i:61616

 

If the process is still running after shutdown, kill the pid shown in the output of the command above.