Re: Shutdown Status in Bootstrap/Catalina

[Mark R. Diggory]

Yoav, Craig, and Remmy:

Just curious, is this something that should be added as a feature 
request? Are you in a position to develop such a feature easily? I guess 
I'd  like to hear from Craig or Remmy if they think this idea is logical 
to them, they are primary authors of the 
.startup.Bootstrap/startup.Catalina codebase. Please let me know what 
you guys think, if its not a good idea then I'll try to dig deeper into 
the startup/shutdown shell scripts to come up with a solution for my 
project.

-Mark

Shapira, Yoav wrote:

Howdy,
If there is a server thread that can answer, then the answer is true per
your definition, no? 

Or do you mean more precisely, request processing threads on the server?

Yoav Shapira
Millennium ChemInformatics
 

-----Original Message-----
From: Mark R. Diggory [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2003 10:16 AM
To: Tomcat Developers List
Subject: Re: Shutdown Status in Bootstrap/Catalina
I was thinking strictly of only if there were server threads/processes
up. Nothing to do with the state of the contents of those processes
(webapps), just a straight boolean presence/absence of processes. In
this sense it would do the following
If server process/threads exist - return true
If server process/threads do not exist - return false
This would be just enough granularity to make decent decisions about
when to call start in a restart (stop, wait till status==false, and
start) command.
-Mark

Shapira, Yoav wrote:

   

Howdy,
What would you suggest as the possible outputs from the status
     

command?
 

Personally, every time I've tried something like this I've run into
granularity problems.  Is the status "ok" when there is a server
process, when the server manager webapp is available, or when user
webapps are all available, or some subset thereof?  If the server is
     

not
 

running, how will you get a status back?  Etc etc.

Yoav Shapira
Millennium ChemInformatics


     

-----Original Message-----
From: Mark R. Diggory [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2003 9:28 AM
To: [EMAIL PROTECTED]
Subject: Shutdown Status in Bootstrap/Catalina
Hi All,

We're looking into the possibility of improving the
       

Bootstrap/Catalina
 

startup/shutdown that is currently used to start/stop tomcat in the
JPackage RPM distribution for Tomcat 4.l.*.
What are the chances that a "status" command could be added to the
Bootstrap/Catalina 4.1.* classes? This would allow us to check the
status of tomcat while shutting down in the shutdown scripts. For
scripts that start/stop/restart tomcat as an init.d service (Redhat),
the script would then be more capabile of waiting for tomcat to shut
completely down before restarting becuase it wait until the status
       

changed.

     

As it is now, when lots of things happen on shutdown, using a shell
script "sleep" command to wait for shutdown before 'restarting'
       

causes
 

the startup to start before the shutdown has fully completed. Having
       

a
 

status command would give script developers better control over when
tomcat has really completely shutdown. Administrators wouldn't have
       

to
 

go in and muck around with the scripts sleep time when their
webapps/connectors require more time to shutdown.
Thanks,
-Mark Diggory
HMDC
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
       



This e-mail, including any attachments, is a confidential business
     

communication, and may contain information that is confidential,
proprietary and/or privileged.  This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else.  If you are not the(an)
   

intended
 

recipient, please immediately delete this e-mail from your computer
   

system
 

and notify the sender.  Thank you.
   

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


     

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   





This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged.  This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender.  Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]