Hi You could have looked at the Camel JMS docu as well. There is a big red warning block http://camel.apache.org/jms
Also, if you are using XA resources or running in a J2EE container, you may want to set the cacheLevelName to be CACHE_NONE as we have found that when using JBoss with TibCo EMS and JTA/XA you must disable caching. On Thu, Feb 24, 2011 at 8:14 AM, Bill <[email protected]> wrote: > > HI, > I resolved this error. > > add <property name="cacheLevelName" value="CACHE_NONE"></property> in > JMSComponent. > > because JMSComponent use DefaultMessageListenerContainer in spring , and in > spring'docs , there is a words: > Currently known servers that absolutely require CACHE_NONE for XA > transaction processing: JBoss 4. For any others, consider raising the cache > level. > so only using CACHE_NONE ,the XA can work. > -- > View this message in context: > http://camel.465427.n5.nabble.com/JMS-Transaction-in-jboss-camel-is-not-work-tp3395258p3398128.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
