This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Sebastian.Kreft.Deezer
Recipients Sebastian.Kreft.Deezer, bquinlan, glangford, mark.dickinson, pitrou, python-dev, sbt, tim.peters, vstinner
Date 2014-06-16.09:24:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402910674.39.0.535355561489.issue20319@psf.upfronthosting.co.za>
In-reply-to
Content
Any ideas how to debug this further?

In order to overcome this issue I have an awful workaround that tracks the maximum running time of a successful task, and if any task has been running more than x times that maximum I consider it defunct, and increase the number of concurrent allowed tasks. However, if the problem persist, I eventually will have lot of zombie tasks, which will expose some additional problems.
History
Date User Action Args
2014-06-16 09:24:34Sebastian.Kreft.Deezersetrecipients: + Sebastian.Kreft.Deezer, tim.peters, bquinlan, mark.dickinson, pitrou, vstinner, python-dev, sbt, glangford
2014-06-16 09:24:34Sebastian.Kreft.Deezersetmessageid: <1402910674.39.0.535355561489.issue20319@psf.upfronthosting.co.za>
2014-06-16 09:24:34Sebastian.Kreft.Deezerlinkissue20319 messages
2014-06-16 09:24:33Sebastian.Kreft.Deezercreate