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. As the person being responsible for the good behavior of applications in production, I expect webapps that I deploy to behave correctly, ie fail to deploy in the event of an initialization failure. Tomcat won't provide me with this information, EXCEPT if I use the manager webapp (in text mode, of course) to deploy it, as I can parse the return "message". [...] > > 'fullstart' is an odd name, people might start using it thinking that > 'start' did not fully start the server. > Which is the case in this particular scenario! OK, maybe not fullstart, but appstart, something else... As long as this command doesn't complete before all webapps configured at startup have attempted a deployment. > Returning an exit code which describes the number of apps successfully > started isn't much use unless you (or the init script) know the number > of apps configured. > No, you misread what I say. What I want is the return code to be the number of webapps NOT successfully deployed. But even that, I reckon, is not that good an idea: the JVM will return 1 in the event of an uncaught exception (or thrown from main()). So, 1+n, where n is the number of webapps not successfully deployed. But in any case, obey the basic principle that 0 means success, and anything else means a failure. -- Francis Galiegue ONE2TEAM Ingénieur système Mob : +33 (0) 683 877 875 Tel : +33 (0) 178 945 552 f...@one2team.com 40 avenue Raymond Poincaré 75116 Paris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
