SwitchYard throws "Could not commit JMS transaction" exception when working with transacted A-MQ JMS queue and an exception takes place
Issue
- It appears that
SwitchYard
does not work well with transactedA-MQ
JMS queue when an exception takes place during message consumption. - Any idea how to best overcome warning messages shown below (which is captured from
server.log
) ? It appears that this is related toJMS transaction
issues.
2014-09-29 14:53:49,503 WARN [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] (pool-7-thread-2) Setup of JMS message listener invoker failed for destination 'queue/TestConsumptionQueue' - trying to recover. Cause: Could not commit JMS transaction; nested exception is javax.jms.IllegalStateException: Not a transacted session
-
The issue still takes place even if the users ensure that same connection factory (i.e.
#activemq/ConnectionFactory
) is not used for all thecamel-jms
bindings inswitchyard.xml
as discussed here in the documentation [1] . -
It works fine if
HornetQ
is used instead ofA-MQ
.
Environment
- Red Hat JBoss Fuse Service Works (FSW)
- 6.0.0
- Red Hat JBoss A-MQ (A-MQ)
- 6.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.