JBossDeveloper

Tim,

Do you know which version of JBoss Messaging contains the fix you mention?
Also is there a corresponding fix in JBoss Remoting as well? If so in which version is it?

We are experiencing similar issues when load testing with JBoss Messaging with usage pattern of JMS connections being very similar (lookup factory, lookup queue, connect to queue, open session, send message, close connection) but we are using a JMS connection max-pool-size of 20 as defined in the tx-connection-factory in jms-ds.xml.

Our environment is :
JBM 1.4.0 SP3
JBoss AS 4.2.2 GA
JDK 1.5.0_06
Redhat Linux
MySQL for JMS persistence
Sybase for data persistence

As mentioned by Kevin Conner the BisocketServerInvoker$ControlMonitorTimerTask and BisocketClientInvoker and HashMaps are growing in number and size throughout the test and never getting GC'd.

Any help is appreciated.

Harish.