tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg <g...@Brim.Net>
Subject Re: Slow startup - Was: Precompiling JSPs for Deployment
Date Wed, 26 Jul 2000 23:32:26 GMT
I could never reply to Olivier.Lefevre@ubsw.com as it seems there is a
problem with the mail server at gate.chi.ubswarburg.com. I'm forwarding
this to the list in hopes that he will see it, since he was responding to
a message I had posted here before...

Greg Holt


The original message was received at Fri, 21 Jul 2000 17:29:46 -0500
from brim.brim.net [207.71.8.216]

   ----- The following addresses had permanent fatal errors -----
<Olivier.Lefevre@ubsw.com>

   ----- Transcript of session follows -----
451 <Olivier.Lefevre@ubsw.com>... reply: read error from
gate.ldn.ubswarburg.com.
451 <Olivier.Lefevre@ubsw.com>... reply: read error from
gate.chi.ubswarburg.com.
451 <Olivier.Lefevre@ubsw.com>... reply: read error from
gate.opf.ubswarburg.com.
451 <Olivier.Lefevre@ubsw.com>... reply: read error from
gate.stm.ubswarburg.com.
451 <Olivier.Lefevre@ubsw.com>... reply: read error from
gate.sng.ubswarburg.com.
<Olivier.Lefevre@ubsw.com>... Deferred: Connection reset by
gate.sng.ubswarburg.com.
Message could not be delivered for 5 days
Message will be deleted from queue

    [ Part 2: "Delivery Status" ]

Reporting-MTA: dns; brim.brim.net
Arrival-Date: Fri, 21 Jul 2000 17:29:46 -0500

Final-Recipient: RFC822; Olivier.Lefevre@ubsw.com
Action: failed
Status: 4.4.7
Remote-MTA: DNS; gate.sng.ubswarburg.com
Last-Attempt-Date: Wed, 26 Jul 2000 18:23:47 -0500


    [ Part 3: "Included Message" ]

Date: Fri, 21 Jul 2000 17:29:45 -0500 (CDT)
From: Greg <greg@Brim.Net>
To: Olivier.Lefevre@ubsw.com
Subject: Re: Slow startup - Was: Precompiling JSPs for Deployment

Whew! Well, that's a long story. But the break-point was simply waiting
for the busy period and hitting ctrl-\ to see what was running at the
time. :) I noticed the randomizer code was running, waited a second, hit
ctrl-\ again and it was still running. From there it was a matter of
tracking down what in the source was using the randomizer...

The proof was when I put in my fix and everything ran quickly.

Greg Holt




> And can you tell us exactly how you found the problematic code portion?
> 
> Thanks,
> 
> -- O.L.




Mime
View raw message