You have to send it a signal that it will respond to, after 'stopwaitsecs' supervisord should send it a SIGKILL which should kill any process. So either you've set stopwaitsecs=0, which IIRC will wait forever or supervisord isn't able to get an exit status from java after sending a SIGKILL--which means that java is buried in a device driver or file system driver and cannot exit. Having hard drive problems?
On Fri, May 13, 2011 at 11:33 AM, Bob Corsaro <[email protected]> wrote: > I'm running a java process from supervisor and supervisorctl restart all > doesn't kill the old process. Any tips for dealing with java? > _______________________________________________ > Supervisor-users mailing list > [email protected] > http://lists.supervisord.org/mailman/listinfo/supervisor-users > > _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
