-danch
Scott M Stark wrote:
This is such nonsense I can't believe it. A framework has used ThreadLocals for
whatever reason. It knows nothing about the context in which it is being
used. So just because it happens to be used in the context of an RMI invocation,
every thread, including the non-RMI threads that have touched the ThreadLocal
should be cleared? Implement your ThreadPoolLocal construct and quit whinning.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message ----- From: "Bill Burke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 16, 2003 11:17 AM
Subject: RE: [JBoss-dev] ThreadPooling in JMX? Its broken
"Each thread holds an implicit reference to its copy of a thread-local variable as long as the thread is alive and the ThreadLocal instance is accessible; after a thread goes away, all of its copies of thread-local instances are subject to garbage collection (unless other references to these copies exist). "As a developer you assume the thread will die after run is complete. Or in the case of an RMI invocation, when the invocation returns. The JDK developers were too shortsighted to see that people might implement thread-pools. Otherwise there would be a way to Clear the thread locals associated with a thread.
-------------------------------------------------------
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
