[
https://issues.apache.org/jira/browse/CAMEL-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120760#comment-13120760
]
Claus Ibsen commented on CAMEL-4512:
------------------------------------
You should probably disable consumer cache on the JMS side.
See details here: Transactions and Cache Levels
http://camel.apache.org/jms
eg set cacheLevelName=CACHE_NONE
> Issue by shutdown for XA connection between MQ Series and Oracle (Bitronix
> transaction manager)
> -----------------------------------------------------------------------------------------------
>
> Key: CAMEL-4512
> URL: https://issues.apache.org/jira/browse/CAMEL-4512
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.5.0
> Environment: Camel 2.5 on Windows XP
> MQSeries 5.3 (Unix)
> Oracle 11 (Unix)
> Bitronix Transaction manager
> Reporter: Benoit Bordonne
>
> Using the Bitronics transaction manager to create an XA connection between
> MQSeries 5.3 and Oracle 11 to manage follwowing actions within one
> transaction:
> - dequeue a message from a MqSeries queue
> - Write the content in the DB
> This works fine (message is dequeued and written in the DB), from an external
> client it is possible to check that the message does not exist in the queue
> anymore.
> When the Camel context is shutdown, the messages appear again in the queue.
> Using the same code in Camel 2.8, it is working fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
