2011/6/16 Francis GALIEGUE <f...@one2team.com>: > On Thu, Jun 16, 2011 at 12:29, Pid <p...@pidster.com> wrote: > [...] >> >> An application might report that it's started, even it hasn't finished >> initialising. >> > > That is the application's responsibility, so not the problem at hand. > > Furthermore, if the application reports a successful start even though > it is not completely initialized, i consider this an application > fault, therefore not my concern.
Some resources are allocated only on the first access. E.g. starting servlets, or obtaining database connections from a pool. Unless you obtain a connection there is no knowing that the database is accessible. 1) Consider implementing a Listener. 2) Note the bindOnInit option on Connector http://tomcat.apache.org/tomcat-7.0-doc/config/http.html though binding while Tomcat initializes is necessary to be able to access privileged ports. If Tomcat is run with jsvc, jsvc drops the privileges once the initialization succeeds. 3) There was once discussion on this list about starting Connectors programmatically. That is, Tomcat starts without connectors (or with stopped connectors), somewhat like a hot standby, and starts the connectors when everything else is ready. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
