Richard, that's pretty much it then, except that you can create a custom
logger to catch stdout and stderr if you want; refer to the manuals for
that.
You can usually tell if JRun shutdown or got torched.On a graceful
shutdown, the destroy methods of servlets will be invoked, including the
With the JRun server shutdown during this time, you'd see errors on the
Apache side without corresponding errors on the JRun side (Apache was
fielding and forwarding requests to JRun, but JRun wasn't running and wasn't
logging problems).The only way to determine what happened relative to JRun
is
I believe that you might find more logging info if you run from the
command line and redirect stdout and stderr to a file.With JRun3 these
used to be captured in a separate log files, but with JRun4 this is no
longer the default.I do believe that the documentation talks about how
to setup such
Ben Groeneveld wrote:
I believe that you might find more logging info if you run from the
command line and redirect stdout and stderr to a file.With JRun3 these
used to be captured in a separate log files, but with JRun4 this is no
longer the default.I do believe that the documentation
Rchard, I'm not sure by what you mean to say in that logging is always
on, and println() for System.out and System.err will go to stdout and
stderr, so I suspect that if you redirect them you will capture them.
All other logging should be in JRun4/logs.Does that make sense?BenG.
Richard
Ben Groeneveld wrote:
Rchard, I'm not sure by what you mean to say in that logging is always
on, and println() for System.out and System.err will go to stdout and
stderr, so I suspect that if you redirect them you will capture them.
All other logging should be in JRun4/logs.Does that make
