2009/1/28 chrajanirao <rajan...@gmail.com>: > Hi, > > It seems to me that Spring's DMLC implementation has a flaw/bug when > JmsTransactionManager and CACHE_SESSION is used. It seems, spring is > creating a session upfront once as we have cache session and a new session > for every message in JmsTransactionManager. The cached session is being used > for receiving. Hence if you don't specify sessionTransacted=true but supply > the TX manager, the non-transacted cached session is used for consuming > messages. This is a serious problem.
Let me just check I follow you. You're saying there is a problem if you don't want to use transacted sessions but do want to use CACHE_SESSION, then DMLC creates a new session each time due to the presence of teh JmsTransactionManager right? If thats the case, its easy to work around in Camel; we can just not configure the transaction manager if transacted = false right? > Although this is a spring issue, I wanted to bring it up here as Camel is > enforcing that you supply a Tx manager when sessionTransacted=true and it > degrades performance by creating a new session evetytime and not even use it > consume messages. Oh hang on are you saying Spring creates a new session every time when using transacted=true? -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
