[
https://issues.jenkins-ci.org/browse/JENKINS-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160226#comment-160226
]
Uwe Stuehler commented on JENKINS-9621:
---------------------------------------
Just for the record: We have also avoided the issue altogether by switching
from Tomcat to Winstone. I am not sure however if it was something in our
Tomcat/Tanuki configuration or something else.
> Restart after plugin installation shuts Tomcat down
> ---------------------------------------------------
>
> Key: JENKINS-9621
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9621
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Debian 6, Tomcat 7.0.11, Jenkins 1.410
> Reporter: Manuel Doninger
> Priority: Critical
>
> The restart after a plugin installation via the "Restart when no jobs are
> running" button in the Plugin Manager shuts down the complete Tomcat
> instance, but the instance isn't coming up, i have to start it manually.
> I think that Jenkins should not shut down, if it is deployed into a container
> (i don't know if it's possible to determine), rather than let the
> administrator use the container facilities to restart an application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
