[Deploying Sakai] killing threads
hedrick at rutgers.edu
Wed Oct 28 19:25:20 PDT 2009
Of course, given that I typically look at what code is looping, I
could probably use Thread.stop with a signal that makes sense at that
On Oct 28, 2009, at 10:20 PM, Charles Hedrick wrote:
>>> however Thread.stop() is considered unsafe:
>> and even Sun's own disclaimer:
>> which is why I've never even attempted it...
> I read that. However the alternative is to leave the thread in the
> loop. The inconsistency is still there. In addition, the looping
> thread could have some critical data structure locked. In that case
> the JVM (or perhaps one user or one test, etc) could be unusable.
> I've never actually seen that in one of these looping situations.
> There's no really safe alternative other than restarting the JVM,
> and even that could leave the database in an inconsistent state. You
> pays your money and takes your choice.
> production mailing list
> production at collab.sakaiproject.org
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the production