-
Bug
-
Resolution: Done
-
Major
-
7.2.4.GA
-
-
-
-
-
-
-
-
Incorporated by upgrade to org.jboss.genericjms 2.0.4
When a message broker such as SonicMQ (which does not support JMS 2.0) is used with the generic-jms-ra , it doesn't work and the following exception is thrown:
Caused by: java.lang.AbstractMethodError: progress.message.jclient.QueueConnectionFactory.createContext(Ljava/lang/String;Ljava/lang/String;)Ljavax/jms/JMSContext;
at org.jboss.resource.adapter.jms.JmsManagedConnection.createConnection(JmsManagedConnection.java:774)
at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:666)
at org.jboss.resource.adapter.jms.JmsManagedConnection.<init>(JmsManagedConnection.java:189)
It seems that JMS 2.0's createContext() is called while creating a new connection which results in the aforementioned exception.
- clones
-
JBEAP-18192 [GSS](7.3.z) Generic RA does not support JMS 1.1 in EAP 7.x
- Closed
- is incorporated by
-
JBEAP-19120 [GSS](7.2.z) Upgrade org.jboss.genericjms from 2.0.2.Final-redhat-00001 to 2.0.4.Final-redhat-00001
- Closed
-
JBEAP-19587 [GSS](7.2.z) Upgrade org.jboss.genericjms from 2.0.2.Final-redhat-00001 to 2.0.6.Final-redhat-00001
- Closed
- is related to
-
JBEAP-18191 [GSS](7.2.z) Generic RA ManagedConnection opens 2 connections to the broker
- Closed