Hi Rainer a very big thanks for your help, and also for your work in the connector project. My work and passion depends on your work: I will never thank enough you and the many people working on opensource projects like tomcat.
I will test the new version as soon as it's released. Best regards Enrico On 19/11/06, Rainer Jung <[EMAIL PROTECTED]> wrote:
Hi Enrico, I think we will have fixed your original problem, and also the sendfull/another log lines in 1.2.20. They don't mean anything bad, so please ignore them for the moment. Watch the list, we will have a 1.2.20 release ready for testing next week. Concerning the client write error, this usually neans, that the response of a request could not be sent successfully to the client. Typically the client is a browser and most often the source of the problem is a request that runs for a longer time, than exected by the user. So the user presses "Again" or clicks on another link. The browser then closes the current connection and starts a new one. Trying to send back addinitional response packets for the first request then detects the closed connection and throws an info message. If this explanation fits into what you are experiencing, then you can ignore these messages two. They won't go away in 1.2.20, because it is important to know, if this happens only rarely, or very often. In the apache access log you can log the response times with %D so you can get an idea, if most occurences relate to long running requests. Regards, Rainer
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
