Bug#402603: tomcat5.5: blocks on startup until log pipe is read

[Loïc Minier]

On Tue, Dec 12, 2006, Marcus Better wrote:
> >  It's usually to diagnose startup problems.
> I propose that we add a debug mode, disabled by default, in which we send 
> stdout and stderr to a regular file, or even the named pipe, and tell the 
> user to read it manually.
> 
> In normal operation we ignore stdout and stderr. There is no reason for 
> daemons to print stuff to stdout and expect someone tp read it, and the 
> regular logging mechanism in Tomcat is excellent.

 But you need to bootstrap it somehow, and during the bootstrap, there's
 usually a "simple" logger which logs to stdout.  I found this blog post
 on the subject interesting:
    <http://pezra.barelyenough.org/blog/2005/03/java-daemon/>

 I don't how well it maps to tomcat5.5 in particular, but it seems to me
 it has a "Bootstrap" in catalina and some shell redirections for the
 initial messages.  I suppose what one could typically see in these
 messages could be "could not load internal class xyz".

 Once the daemon is bootstrapped, it will open its regular log files (as
 configured), and close its stdout and stderr indeed.

-- 
Loïc Minier <lool at dooz.org>
 "I have no strong feelings one way or the other." -- Neutral President