incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BIGTOP-537) provide a workaround for non-LSB compliant catalina.sh handling of a stop action
Date Tue, 17 Apr 2012 16:47:19 GMT

     [ https://issues.apache.org/jira/browse/BIGTOP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Roman Shaposhnik updated BIGTOP-537:
------------------------------------

    Attachment: BIGTOP-537.patch.txt
    
> provide a workaround for non-LSB compliant catalina.sh handling of a stop action
> --------------------------------------------------------------------------------
>
>                 Key: BIGTOP-537
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-537
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-537.patch.txt
>
>
> Turns out that the default catalina.sh stop action is a weird in how it handles a missing
PID file:
> {noformat}
>  if [ ! -z "$CATALINA_PID" ]; then
>     if [ -f "$CATALINA_PID" ]; then
>     ...
>     else
>       echo "\$CATALINA_PID was set but the specified file does not exist. Is Tomcat running?
Stop aborted."
>       exit 1
>     fi
>   fi
> {noformat}
> This, effectively, means that one can't stop an already stopped service cleanly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message