Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #14859

Re: Proposed new Java feature

Show all headers | View raw

On 05/28/2012 12:27 AM, Tom Anderson wrote:
> On Sun, 27 May 2012, Eric Sosman wrote:
>
>> If you think of anything new to add, pray do so.
>
> Mike added this pithy statement of the goal:
>
> Or, to say it another way, when getting a Thread from a ThreadPool, it
> should be completely indistinguishable whether it's a recycled or
> brand-new thread.
>
> At the moment, it is *not* possible to achieve that, because
> ThreadLocals will survive recycling.

But that is actually a good thing: ThreadLocal's purpose is to attach 
state to a thread which can be accessed without synchronization (if not 
shared).  Consider attaching a database connection to a thread.  It 
would be disastrous for the connection itself to just clear the object 
reference through some global "remove all" and you would pay a high 
price for opening new connections over and over again.  If the database 
connection is supposed to be attached to a thread for only a certain 
amount of time (e.g. a method call) then it must be coded to be properly 
cleaned up; in case of a JDCB connection that means invoking commit() or 
rollback() and then close().  Only after that you can safely clear the 
reference.  But this entirely depends on the ThreadLocal at hand and 
needs to be done specifically for individual ThreadLocals - it cannot be 
done globally.

> One way of looking at a thread pool is that it provides a supply of
> fresh short-lived virtual threads, implemented on top of long-lived real
> threads. Every time we take a thread out of the pool, we want it to
> appear brand-new. Deleting all ThreadLocals when a real thread is
> recycled is not "extremely dangerous", because at that moment, the
> *virtual* thread is dying, and a new one is being created; that makes it
> an entirely appropriate thing to do.

It *is* dangerous as I have explained above.  The observable state of 
each of these virtual threads should of course be identical but that 
does not mean that the technical state must be identical (that's 
basically what caching is all about).  For example, in case of the DB 
connection you might open the connection in initialValue() or some other 
logic so the code using the ThreadLocal always sees a properly 
initialized connection.

> It is certainly true that it is "only a crutch for not doing the right
> thing to begin with", but the sad fact is that programmers persist in
> not doing the right thing to begin with, and it is useful for framework
> writers to be able to limit the damage they can cause.

Actually the global remove would cause more damage than it prevents. 
You cannot know about all the other ThreadLocals used in code and a 
framework writer who attempts to just clear state of other modules 
without even knowing them should be tarred and feathered.

Cheers

	robert

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Proposed new Java feature "Mike Schilling" <mscottschilling@hotmail.com> - 2012-05-26 16:11 -0700
  Re: Proposed new Java feature Robert Klemme <shortcutter@googlemail.com> - 2012-05-27 13:32 +0200
    Re: Proposed new Java feature "Mike Schilling" <mscottschilling@hotmail.com> - 2012-05-27 11:14 -0700
      Re: Proposed new Java feature Robert Klemme <shortcutter@googlemail.com> - 2012-05-28 12:13 +0200
      Re: Proposed new Java feature v_borchert@despammed.com (Volker Borchert) - 2012-06-04 20:16 +0000
  Re: Proposed new Java feature markspace <-@.> - 2012-05-27 09:28 -0700
    Re: Proposed new Java feature "Mike Schilling" <mscottschilling@hotmail.com> - 2012-05-27 11:00 -0700
      Re: Proposed new Java feature Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-05-27 11:46 -0700
        Re: Proposed new Java feature "Mike Schilling" <mscottschilling@hotmail.com> - 2012-05-27 12:04 -0700
          Re: Proposed new Java feature Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-05-27 15:30 -0400
            Re: Proposed new Java feature "Mike Schilling" <mscottschilling@hotmail.com> - 2012-05-27 12:59 -0700
              Re: Proposed new Java feature Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-05-27 17:51 -0400
                Re: Proposed new Java feature markspace <-@.> - 2012-05-27 15:20 -0700
                Re: Proposed new Java feature Robert Klemme <shortcutter@googlemail.com> - 2012-05-28 12:13 +0200
                Re: Proposed new Java feature markspace <-@.> - 2012-05-28 08:28 -0700
                Re: Proposed new Java feature Robert Klemme <shortcutter@googlemail.com> - 2012-05-28 19:29 +0200
                Re: Proposed new Java feature markspace <-@.> - 2012-05-28 12:16 -0700
                Re: Proposed new Java feature Robert Klemme <shortcutter@googlemail.com> - 2012-05-28 22:58 +0200
                Re: Proposed new Java feature "Mike Schilling" <mscottschilling@hotmail.com> - 2012-05-28 21:40 -0700
                Re: Proposed new Java feature Robert Klemme <shortcutter@googlemail.com> - 2012-05-29 22:52 +0200
                Re: Proposed new Java feature "Mike Schilling" <mscottschilling@hotmail.com> - 2012-05-29 18:53 -0700
                Re: Proposed new Java feature Tom Anderson <twic@urchin.earth.li> - 2012-05-27 23:27 +0100
                Re: Proposed new Java feature Robert Klemme <shortcutter@googlemail.com> - 2012-05-28 12:22 +0200
                Re: Proposed new Java feature "Mike Schilling" <mscottschilling@hotmail.com> - 2012-05-27 21:43 -0700
                Re: Proposed new Java feature Andreas Leitgeb <avl@gamma.logic.tuwien.ac.at> - 2012-05-29 14:32 +0000
  Re: Proposed new Java feature Tom Anderson <twic@urchin.earth.li> - 2012-05-27 18:43 +0100
  Re: Proposed new Java feature Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2012-06-02 12:41 -0700
    Re: Proposed new Java feature markspace <-@.> - 2012-06-02 15:55 -0700

csiph-web