Not that it makes it impossible to make Terracotta's hook run last, but shutdown hooks are allowed to run in parallel.
In case we're pursuing this area further, one can get into trouble with finalizers being run at exit too. To allow shared object actions in a finalize() at VM exit time would mean we'd have to delay terracotta shutdown even further. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:tc-dev- > [EMAIL PROTECTED] On Behalf Of Steven Harris > Sent: Tuesday, August 28, 2007 11:58 AM > To: Prasad Bopardikar > Cc: [email protected] > Subject: Re: [tc-dev] Shutdown hook Thread > > In order for Terracotta to make sure that all actions taken in the > process before exiting are fully sent out it has it's own shutdown hook > for flushing. I think we might be able to make sure our shutdown hook > runs last and allow people to do things in their own shutdown > hook. > > That said, I'm curious why you need a shutdown hook in a terracotta > world? > > Cheers, > Steve > > On Aug 28, 2007, at 11:52 AM, Prasad Bopardikar wrote: > > > Why does Terracotta not allow a shutdown hook thread to update a > > shared object? > > > > > > > > > > _______________________________________________ > > tc-dev mailing list > > [email protected] > > http://lists.terracotta.org/mailman/listinfo/tc-dev > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
