[BUG] JMS Listener/Reader no longer works with ActiveMQ

[fallensieg]

Describe the bug
JMS Sender/Listener channels no longer work with ActiveMQ.

To Reproduce
I have several JMS Sender / Listener channels with ActiveMQ (5.15.11) working fine in Mirth 4.0.1
Now I'm trying to upgrade Mirth to 4.4.2 and when I try to send a message to ActiveMQ I get the error:
org.apache.activemq.ActiveMQConnectionFactory cannot be cast to javax.jms.ConnectionFactory

imatge.png​

I've tried to downgrade to Mirth 4.3 and the error is the same, but with Mirth 4.2 it works again. Have also tired upgrading to 4.5, same problem.
Am I doing something wrong, or could it be a bug from Mirth 4.3 and above?
Anyone knows a workaround for this issue?

Expected behavior
JMS Listener and Sender can read/write messages against ActiveMQ.

Actual behavior
Channels will not even start with the following error message

Caused by: java.lang.ClassCastException: class org.apache.activemq.ActiveMQConnectionFactory cannot be cast to class javax.jms.ConnectionFactory (org.apache.activemq.ActiveMQConnectionFactory is in unnamed module of loader com.mirth.connect.server.util.ChildFirstURLClassLo ader @17f0d6e; javax.jms.ConnectionFactory is in unnamed module of loader java.net.URLClassLoader @3970ed7e) at com.mirth.connect.connectors.jms.JmsClient.start(J msClient.java:129)

Environment (please complete the following information):

• OS: Windows 10
• Java: OpenJDK 11
• Connect Version : anything above 4.0.1

Workaround(s)
Would be intered in knowing.

Additional context
Add any other context about the problem here.

[pacmano1]

Maybe upload a sample channel?

[ab-mg-23]

The problem is using a resource to load the ActiveMQ Client library and commit fd3b7b2 changing the child classloader to take effect before the cast from the concrete ActiveMQConnectionFactory to the ConnectionFactory interface. The interface definition is in a different classloader than the concrete definition, so Java throws an error on the cast. If you move the client JAR and dependencies into server-lib/jms that should load everything from the same classloader as a workaround, but then run the risk of classpath issues with dependencies.

[fallensieg]

Thank you @ab-mg-23. That was exactly the issue and doing what you've suggested has resolved my problem.

[hae-anyoung]

Adding this for reference. More people are seeing this issue. https://forums.mirthproject.io/forum/mirth-connect/support/184548-jms-sender-and-activemq

[hae-anyoung]

If you move the client JAR and dependencies into server-lib/jms that should load everything from the same classloader as a workaround, but then run the risk of classpath issues with dependencies.

This didn't work for me. Still getting the ClassCastException