Unable to connect to an ActiveMQ broker via the AMQP protocol

It is not possible to connect to an ActiveMQ broker via the AMQP transport when using the Generic JMS Adapter with the ActiveMQ client libraries. The following exception is retuned in the Generic JMS Adapter server log file:

Caused by: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:5672
at org.apache.activemq.transport.amqp.AmqpInactivityMonitor$1$1.run(AmqpInactivityMonitor.java:69)

According to the exception in the Generic JMS Adapter server log file, it is trying to connect via the TCP transport (e.g. tcp://127.0.0.1:5672) instead of the AMQP transport (e.g. amqp://127.0.0.1:5672).
 

The AMQP transport has been enabled in the activemq.xml configuration file.

The URL which is passed to the ABL setBrokerURL JMS-API procedure is similar to the following: amqp://localhost:5672 .


 

The ActiveMQ client libraries do not support the AMQP protocol.

The use of the Apache "Qpid JMS (javax.jms)" client libraries is required (see https://qpid.apache.org/download.html) to be able to connect to the ActiveMQ broker via the AMQP transport. However, the Generic JMS Adapter currently requires the use of JNDI and JMS Administered Objects in order for it to work successfully with the Qpid JMS client libraries. Please refer to the following KB article for more information:

Sample code and setup for using Apache QPID JMS client with OpenEdge Generic JMS adapter
 

Progress Article(s):
The Generic JMS Adapter does not work with the QPID JMS Provider
ABL-JMS example with ActiveMQ
Generic JMS Adapter connection to ActiveMQ 5.17.x fails