In OpenEdge 12.6, the Generic JMS Adapter (ClientConnect) will always use the [SonicMQ] section in the %DLC%\properties\jmsProvider.properties file even though the -DjmsProvider JVM parameter is set to another JMS provider.

Assume the following %DLC%\properties\jmsProvider.properties:

[WebsphereMQ]
javax.jms.ConnectionFactory=com.ibm.mq.jms.MQConnectionFactory
javax.jms.QueueConnectionFactory=com.ibm.mq.jms.MQQueueConnectionFactory
javax.jms.TopicConnectionFactory=com.ibm.mq.jms.MQTopicConnectionFactory

[ActiveMQ]
javax.jms.ConnectionFactory=org.apache.activemq.ActiveMQConnectionFactory
javax.jms.QueueConnectionFactory=org.apache.activemq.ActiveMQConnectionFactory
javax.jms.TopicConnectionFactory=org.apache.activemq.ActiveMQConnectionFactory

[SonicMQ]
javax.jms.ConnectionFactory=org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory
javax.jms.QueueConnectionFactory=org.apache.activemq.artemis.jms.client.ActiveMQQueueConnectionFactory
javax.jms.TopicConnectionFactory=org.apache.activemq.artemis.jms.client.ActiveMQTopicConnectionFactory

[HornetQ]
javax.jms.ConnectionFactory=org.hornetq.jms.client.HornetQJMSConnectionFactory
javax.jms.QueueConnectionFactory=org.hornetq.jms.client.HornetQQueueConnectionFactory
javax.jms.TopicConnectionFactory=org.hornetq.jms.client.HornetQTopicConnectionFactory

[ArtemisMQ]
javax.jms.ConnectionFactory=org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory
javax.jms.QueueConnectionFactory=org.apache.activemq.artemis.jms.client.ActiveMQQueueConnectionFactory
javax.jms.TopicConnectionFactory=org.apache.activemq.artemis.jms.client.ActiveMQTopicConnectionFactory

[Qpid]
javax.jms.ConnectionFactory=org.apache.qpid.jms.JmsConnectionFactory
javax.jms.QueueConnectionFactory=org.apache.qpid.jms.JmsConnectionFactory
javax.jms.TopicConnectionFactory=org.apache.qpid.jms.JmsConnectionFactory

Assume the following section in the %DLC%\properties\JavaTools.properties file:

[SonicMQ]
classpath=C:\apache-artemis-2.21.0\lib\client\artemis-jms-client-all-2.21.0.jar;${DLC}/sonic/MQ10.0/lib/sonic_Client.jar;${DLC}/java/progress.jar
jvmargs=-DsonicMQExtensions=false -DjmsProvider=ArtemisMQ

If code similar to the following is executed, then the Connection Factory of the ArtemisMQ section in the %DLC%\properties\jmsProvider.properties should be used:

DEFINE VARIABLE jmssession AS HANDLE.
DEFINE VARIABLE messageH AS HANDLE.
DEFINE VARIABLE lDebug AS LOGICAL.

/* Creates a session object. */
RUN jms/jmssession.p PERSISTENT SET jmssession("-SMQConnect").

/* The format for broker URL  with ActiveMQ is tcp://hostname:port. */
RUN setBrokerURL IN jmssession (INPUT "tcp://localhost:61616").

/* Set user credentials. */
RUN setUser IN jmssession (INPUT "admin").
RUN setPassword IN jmssession (INPUT "admin").

/* Connect to the broker. */
RUN beginSession IN jmssession.

/* Create a text message */
RUN createTextMessage IN jmssession (OUTPUT messageH).
RUN setText IN messageH ("This is test message sent.").

/* Send the message to the "MyQueue1" queue */
RUN sendToQueue IN jmssession ("MyQueue1", messageH, ?, ?, ?).

/* Clean up */
RUN deleteMessage IN messageH.
RUN deleteSession IN jmssession.

Instead the following error is returned:

Error connecting to the JMS AppServer service.

If the brkrLoggingLevel=4 and srvrLoggingLevel=4 properties are set in the [Adapter.CC.cc1] section of the %DLC%\properties\JavaTools.properties file, then the following exception will be shown in the cc.server-<PID>.log file:
 

java.lang.Exception: progress.message.jclient.QueueConnectionFactory class file not mentioned correctly: java.lang.ClassNotFoundException: progress.message.jclient.QueueConnectionFactory
    at com.progress.messaging.jms.jms.createQueueFactory(jms.java:219)
    at com.progress.messaging.jms.jms._connect(jms.java:314)
    at com.progress.javafrom4gl.implementation.JavaServlet.<init>(JavaServlet.java:81)
    at com.progress.javafrom4gl.implementation.ServiceImpl.createConnectionServlet(ServiceImpl.java:106)
    at com.progress.ubroker.broker.ubServerThreadIPC.write(ubServerThreadIPC.java:433)
    at com.progress.ubroker.broker.ubASserverThread.processConnect(ubASserverThread.java:574)
    at com.progress.ubroker.broker.ubServerThread.processEvent(ubServerThread.java:1210)
    at com.progress.ubroker.broker.ubServerThread.mainline(ubServerThread.java:479)
    at com.progress.ubroker.broker.ubServerThread.run(ubServerThread.java:356)

 

This issue does not occur in OpenEdge 12.2.

Issue was caused by a product defect.
 

Upgrade to OpenEdge 12.8 or later.