tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 4382] New: - Starting up twice prevents stopping
Date Wed, 24 Oct 2001 00:10:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4382>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4382

Starting up twice prevents stopping

           Summary: Starting up twice prevents stopping
           Product: Tomcat 3
           Version: 3.3 Final
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Config
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: jeff@socialchange.net.au


(Only applicable on *nix, I think)

I've found that if by accident, I run "startup.sh" when Tomcat is already
running, I can no longer shut Tomcat down with "shutdown.sh":

[jeff@kermit bin]$ ./shutdown.sh 
Using classpath: ./../lib/tomcat.jar
Using JAVA_HOME: /usr/local/jdk
Using TOMCAT_HOME: ..
Stopping Tomcat.
Can't read ../conf/ajp12.id

The same thing happens if I run "./tomcat.sh start -jkconf" when Tomcat is
already running.

The problem is that the first thing tomcat.sh does is remove ajp12.id,
regardless of whether the tomcat invocation is successful or long-running. A few
solutions..
 1 Ditch the whole ajp12.id system and make it 'stateless' like Tomcat 4.
 2 Have tomcat.sh check for the '-jkconf' flag, and not remove ajp12.id if so.
 3 Have './tomcat.sh start -jkconf' write a flag file to indicate that it
succeeded. Then tomcat.sh could delete this before, and check for this after.
successful. 

1 would be nicest, but I suppose 2 is most practical.. if you agree but don't
like shell hacking, I can have a go.

--Jeff

Mime
View raw message