Bug#817909: Restarting tomcat7 on Debian 8 does not always stop current running process, resulting in the service entering a failed state

[Emmanuel Bourg]

Control: forcemerge 832151 -1

Le 11/03/2016 à 14:08, Emlyn Kinzett a écrit :

> It looks as though when the restart command is invoked, the current
> process is not stopped correctly and therefore a new process cannot be
> started (this line: java.net.BindException: Address already in use
> <null>:8080). tomcat7 was already listening on port 8080 because it
> wasn’t stopped, so couldn’t be started.

I've run into similar issues too, systemd didn't track properly the
state of the Tomcat instance spawned by the init.d script. I think this
issue will go away once we provide a proper systemd service file for
Tomcat. I'm currently experimenting with this and it works rather well.

Emmanuel Bourg