HIVEMIND-161 (ThreadLocal object not removed on webapp reload) was fixed in Hivemind 1.1.1, but Tapestry 4.0 was not able to make use of it because it did not call the cleanupThread() method (??) or similar.
See http://issues.apache.org/jira/browse/HIVEMIND-161 and see Howard's comments down the bottom. Specifically, he says "I suspect there will be a HiveMind 1.1.1, and a Tapestry 4.0.1 to make use of it". So I was wondering if this has in fact been fixed for Tapestry 4.0.1, since I didn't see any mention of it in the Tapestry 4.0.1 changelog. -Scott On Monday 03 April 2006 11:08, Jesse Kuhnert wrote: > The double checked locking bugs were fixed in 3.0.4, but I don't know of > any specific issues related to performance.. > > Did you have something in mind? > > On 4/2/06, Scott Russell <[EMAIL PROTECTED]> wrote: > > Does Tapestry 4.0.1 make use of the bugfixes to Hivemind1.1 (available as > > Hivemind 1.1.1) that improved performance/prevented certain memory leaks? > > > > Scott > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
