https://issues.apache.org/bugzilla/show_bug.cgi?id=51587
--- Comment #1 from Christopher Schultz <ch...@christopherschultz.net> 2011-08-01 18:24:38 UTC --- I'd like to see more structured data available in the response. Either in CSV/TSV or in XML (maybe selectable via a request parameter/header). I'm not sure why you'd use a non-daemon waiting loop, instead of a simple single-threaded daemon listener. Is that because you want this status listener to be able to reply with a "Tomcat connector dead" response or something like that? I figure that if no connectors start, Tomcat should probably die and the "Tomcat is dead" response would just be a connection failure. There is no need for a "shutdown" command on this port IMO. Maybe you could just re-purpose the existing shutdown listener entirely and add more commands that it recognizes, like "STATUS" and "UPTIME" (though one might argue that those are really the same command). This is likely to require re-factoring because, as you mention, you can't SHUTDOWN before Tomcat has fully initialized anyway. Being able to shut down Tomcat before startup completes (for example, under a faulty configuration that stalls forever while starting up) would be a good thing to be able to do. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
