It looks like the max size of the pool is still hard coded to 25. This should really be exposed as a jmx attribute, but in the mean time can we just use the default constructor for PooledExecutor and now have any max limits. I re-ran my large scale tests with the latest version and still ran into a hang after high load. I changed the JMSServer's PooledExecutor to not have a limit and everything works fine. I also used the default contructor on the PE from Connection (which is hardcoded to 50) just incase. We should probably take another pass at thread clean up, but in the mean time lets not hard code any max sizes, which can cause some applications (like mine) to fail. On a related note, is there any reason why JBossMQService is used instead of directly creating a JMSServer MBean? Do you have any ideas on how to push more of the hard coded parameters that are set (on the PE and others) to jmx attributes? --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
