Tomcat process remains after a start up failure through JSVC
Issue
- When attempting to start up Tomcat through JSVC (daemon.sh), the process remains indefinitely after a start up failure. For instance, with an unparseable server.xml, start up fails and Tomcat is unusable but the process remains:
21-Aug-2018 17:39:16.271 WARNING [main] org.apache.catalina.startup.Catalina.load Catalina.start using conf/server.xml: Element type "className" must be followed by either attribute specifications, ">" or "/>".
21-Aug-2018 17:39:16.271 SEVERE [main] org.apache.catalina.startup.Catalina.start Cannot start server. Server instance is not configured.
Daemon started successfully
java_start done
Waiting for a signal to be delivered
create_tmp_file: /tmp/16518.jsvc_up
- If starting via catalina.sh, the process ends as expected.
Environment
- JBoss Web Server (JWS)
- 3.x
- 5.x
- Tomcat
- 7.0.x
- 8.0.x
- 9.0.x
- JSVC
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
