Hi all, We've been using XA transactions (via atomikos) with JMS component to send/read messages to/from MQ, data is from and saved to oracle database. Now the performance becomes a major problem. We found below from the documentation of camel JMS Component page. Could anyone tell us if it is still true or it is out of date? We're using camel 2.14.2.
Any idea or hints on how to improve the performance would be greatly appreciated. ===================================================== "Transactions and Cache Levels If you are consuming messages and using transactions (transacted=true) then the default settings for cache level can impact performance. If you are using XA transactions then you cannot cache as it can cause the XA transaction to not work properly. If you are not using XA, then you should consider caching as it speeds up performance, such as setting cacheLevelName=CACHE_CONSUMER. Through Camel 2.7.x, the default setting for cacheLevelName is CACHE_CONSUMER. You will need to explicitly set cacheLevelName=CACHE_NONE. In Camel 2.8 onwards, the default setting for cacheLevelName is CACHE_AUTO. This default auto detects the mode and sets the cache level accordingly to: CACHE_CONSUMER = if transacted=false CACHE_NONE = if transacted=true So you can say the default setting is conservative. Consider using cacheLevelName=CACHE_CONSUMER if you are using non-XA transactions." -- View this message in context: http://camel.465427.n5.nabble.com/XA-Transactions-in-Camel-JMS-Component-tp5778406.html Sent from the Camel - Users mailing list archive at Nabble.com.
