Just to give an update to this in case anyone else has a similar issue with the
JMSTemplate. It appears that Spring's recommended solution for caching the actual
connection is to wrap your connection factory in the Spring SingleConnectionFactory
object. This will share the connection across multiple sends and is much better
performing. It still doesn't seem possible to cache at the session level but it's
possible that the next release of Spring might address it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105174#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...