Regarding Spring - that does appear to be what's happening. Trying alternative
approach with the DefaultMessageListenerContainer (again) but without setting a
transactionManager so that it will cache all JMS resources.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104578#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...