Hi guys, I'm posting this to keep track of the issue that when you write connection open/close intensive code, it seems that the GC cannot free up all the resources that is was using. This will be not be an issue if you use pooling of the connections, but if you don't and simple do: lookup factory, lookup queue, connect to queue, open session, send message, receive message, close connection. and you make this loop then you will run out of memory at some point. Both JBM and JBMQ seem to have this problem. From what Kevin could see it may have to do with the way JBoss Remoting is used. Note that we did not look at code; just at what the profiler is telling us. Thanks, --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026650#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...