nikgoodley-ibboost / funcito

Automatically exported from code.google.com/p/funcito
0 stars 0 forks source link

Clean-up after ThreadLocals #75

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
FuncitoDelegate keeps a ThreadLocal InvocationManager.  In Thread Pool 
environments, thread may get reused, and ThreadLocal instance of 
InvocationManager may still be present.  While the state of the thread should 
likely be clean after any complete (correct) call to Fucito, it is is still 
good to call ThreadLocal.remove().  This should probably be done whenever 
FuncitoDelegate.extractInvokableState() is called.

Check framework for other ThreadLocals

Original issue reported on code.google.com by kandpwel...@gmail.com on 24 Oct 2013 at 6:58

GoogleCodeExporter commented 9 years ago
Just for reference:
http://stackoverflow.com/q/13852632/433348
and
http://stackoverflow.com/q/3869026/433348
http://stackoverflow.com/q/5054265/433348
finally:
http://java.dzone.com/articles/painless-introduction-javas-threadlocal-storage

Original comment by kandpwel...@gmail.com on 24 Oct 2013 at 8:14

GoogleCodeExporter commented 9 years ago
done in 1.3.0

Original comment by kandpwel...@gmail.com on 31 Oct 2013 at 6:20