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
builtin JRun servlets, and they log misc things.
If you are running from the console, and JRun looks like it's dead, but
perhaps overloaded as you describe below, you can examine the threads
with Ctrl-Break w/o affecting processing to get an idea of where it's stuck.
Hope that helps, BenG.
Richard Crawford wrote:
> 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 sense? BenG.
>
> I can see that if I ran JRun from the command line, with something like
> "> errorlog", then the error messages will be captured and written to a
> file. I just wish there were a way to retrieve all of those errors that
> are missing from the jrun/log files. The log files I have show no
> reason why JRun should have crashed last Thursday.
>
> Although based on discussions I've had, it looks like JRun didn't crash
> completely; it just seems to have slowed down to such a sluggish pace
> that connections were timing out. I don't understand this at all myself.
>
> For what it's worth, here's the system information, which I should have
> included earlier:
>
> HOST SYSTEM: Solaris 9
> JRUN VERSION: 4 (with updater 3 applied)
> CF VERSION: MX (with updater 2 applied)
> APACHE VERSION: 2.0.45
> DATABASE: SQL Server 7, on a separate WinNT machine
>
> JRun, Apache, and Cold Fusion all live on the same Solaris 9 box.
>
> We are in the process of upgrading our SQL Server database to Oracle 9i
> (and you don't want to know how much of a nightmare that has been).
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
