Uploaded image for project: 'JBoss Web Server'
  1. JBoss Web Server
  2. JWS-1117

Tomcat process remains after bad start up through JSVC

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • JWS 5.0_RHEL_GA, JWS 3.1.0 SP4 GA
    • jsvc, tomcat
    • None
    • -
    • Workaround Exists
    • Hide

      Start with catalina.sh and the process exits with a start up failure.

      Show
      Start with catalina.sh and the process exits with a start up failure.
    • Hide

      -Configure a bad server.xml that can't be parsed
      -Launch via ./daemon.sh

      Show
      -Configure a bad server.xml that can't be parsed -Launch via ./daemon.sh

      The Tomcat process remains after a bad start up through JSVC. For instance, try to start with a bad unparseable server.xml. Tomcat start up errors out, but the process remains indefinitely:

      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

      No ports are available, no tomcat server threads are running. But the java process remains with a no-stack main thread.

      Anyway for the process to terminate after failed start up?

              rhn-support-csutherl Coty Sutherland
              rhn-support-aogburn Aaron Ogburn
              Matus Madzin Matus Madzin
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: