You are correct. I upgrade to spring 2.5, which provides a JMS connection pool. I was
able to successfully create a JMS connection pool that has the same size as my thread pool
for my file reader. After I changed this my error no longer occurs, and I have a
significant performance boost.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151574#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...