demoting these messages to DEBUG, if they are
indeed harmless? Like in this bug report:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16357
> -Original Message-
> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 01, 2003 1:35 PM
> To: Tomcat User
Howdy,
>01-Aug-2003 17:48:01 org.apache.jk.common.ChannelSocket
processConnection
>INFO: Server has been restarted or reset this connection
This were mostly fixed in 4.1.24. Try moving to it (or better yet,
4.1.27), as there are several potentially relevant fixes from 4.1.18.
Yoav Shapira
T
To: "Tomcat Users List" <[EMAIL PROTECTED]>
cc:
Subject: RE: Problems with Tomcat in a high load
environment
Howdy,
Even if your loathe to do it, a profiler is invaluable as long as the
profiled environment (your dev/test env) is close enough to produc
es as well.
Yoav Shapira
Millennium ChemInformatics
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]
>Sent: Friday, August 01, 2003 1:29 PM
>To: [EMAIL PROTECTED]
>Subject: Problems with Tomcat in a high load environment
>
>Hi,
>we are
Hi,
we are running Tomcat 4.1.18 on Windows 2000 under JDK1.4.1_01. We are
using IIS as a web server connecting using the ISAPI JK 2 connector. We
are currently experiencing 2 seperate problems when under high load (ie >
30 requests per second):
1. A huge number of log events (~30 sets per m
