Message9588

Author	stefan.richthofer
Recipients	stefan.richthofer, zyasoft
Date	2015-03-07.13:09:11
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1425733752.46.0.659787385776.issue2280@psf.upfronthosting.co.za>
In-reply-to

Content
This looks like a classical deadlock, so I would suggest a classical solution: Assure that locks are always acquired in the same order by all participants. However, letting runFinalizer() in FinalizeTrigger acquire the monitor of PySystemStateCloser.class should fix it and assure that Finalizers cannot deadlock with PySystemStateCloser in general.

This looks like a classical deadlock, so I would suggest a classical solution:
Assure that locks are always acquired in the same order by all participants.
However, letting runFinalizer() in FinalizeTrigger acquire the monitor of
PySystemStateCloser.class should fix it and assure that Finalizers cannot
deadlock with PySystemStateCloser in general.

History
Date	User	Action	Args
2015-03-07 13:09:12	stefan.richthofer	set	messageid: <1425733752.46.0.659787385776.issue2280@psf.upfronthosting.co.za>
2015-03-07 13:09:12	stefan.richthofer	set	recipients: + stefan.richthofer, zyasoft
2015-03-07 13:09:12	stefan.richthofer	link	issue2280 messages
2015-03-07 13:09:11	stefan.richthofer	create