Starting a new thread for each operation and waiting for garbage collection will result in an event that will look an awful lot like a process table attack to most sysadmins.
'course my sensitivity here is related to my experience on Linux and Windows, where threads are either limited or expensive to create.
-danch
marc fleury wrote:
hmmm
I thought we had cleared the questions of pools of anything long time
ago, meaning that modern VMs take care of that. Also bill, you and I
have been badly burnt in the past by state management in reused
components.
My question would then be 'why would threads be different'?. The usual
reason is that people say "you want to limit how many threads a process
creates, but that can be achieved by just monitoring the number of new
threads created by the pool and listening for notifications on thread
garbage collection calls.
That says that you have pools who just limit the number of threads out
there and block for other but associate a new thread for new
invocations.
marcf
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
