No need. All I'm trying to do is setup a threadpool for all connections rather than have one threadpool per connection.
The threadpool configuration really needs to be externalized from the transport layer. We need to use the threadpool in other places as well, pings for example. I'm just going to do the threadpool configuration on the client via system properties with reasonable defaults. I tried to piggyback the config from the server, but that doesn't work very well and is not very clean. Regards, Adrian View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822712#3822712 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822712 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
