I was wrong, the ReadTask/WriteTask pairs still accumulate, my JConsole was not
refreshing the thread list which lead me to think the problem was over.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4129568#4129568
Reply to the post :
Ok, so here is how I solved the problem.
It is due effectively to the fact that a connection is not closed. I thought I
knew all the points in the application that interacted with JMS, I checked and
double checked them, still there was a place that did its own JMS sending
without closing
Ok, the problem was that the jBPM installation I used did not close connections
after each and every JMS message send it did.
In fact, jBPM JMS subsystem keeps one single Connection and Session for the
whole life of the server application.
The JMS specification says that :
anonymous wrote : A
Ok, I confirm it myself : ASPATCH300 didn't make it in the 4.0.5GA. But, if you
look at the svn rep, you can see that it has been eventually merged :
The history of SocketManager.java in 4.0.5:
