Spring's DefaultMessageListenerContainer doesn't share sessions and consumers between threads, but does share connections. If I'm not mistaken, in your last version you also changed the caching/sharing policy for connections, which are now no longer shared. Is that correct?
Andreas On Fri, Nov 21, 2008 at 18:40, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > > Hi Andreas >>> >>> 1. The JMS Javadocs specify the thread safety characteristics of the >>> Session object as follows: >>> ... >> >> +1.. I agree my intention was to follow the Spring model, and I will fix >> this up.. Thanks for catching this :-) ! > > This is fixed in the private branch, and I also found the cause for the > intermittent issue with the MinConcurrency test, which was a threading bug in > the test. So all tests pass now .. > > I think we are all set to commit this to replace the current code now.. WDYT? > > asankha > > -- > Asankha C. Perera > http://adroitlogic.org > > http://esbmagic.blogspot.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
