Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
To: tomcat-dev@jakarta.apache.org
From: =?ISO-8859-1?Q?Sven_K=F6hler?= <skoehler@upb.de>
Subject: Re: socket errors in catalina.out and mod_jk.log
Date: Thu, 27 Feb 2003 15:50:56 +0100
Lines: 22
Message-ID: <b3l8nb$44t$1@main.gmane.org>
References: <b3gg84$sgb$1@main.gmane.org> <3E5C9554.70109@apache.org>
 <b3irp5$n3$1@main.gmane.org> <3E5DF454.3050408@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.3b) Gecko/20030210
In-Reply-To: <3E5DF454.3050408@apache.org>
Sender: news <news@main.gmane.org>

>> read-error should not happen, as mod_jk could send a quit-paket or 
>> something (analog to the ftp-protocol)
> 
> read-error happen BECAUSE APACHE HTTPD server close client
> when it recycle them.

i hoped, you would react on this one.

i'm not very much into apache httpd's internals, but i guess, that a 
child isn't just killed, but notified to terminate itself (OK, perhaps a 
kill-signal is used), but the question is, if mod_jk is called when a 
child exits/gets killed. if mod_jk can catch this case, it should 
gracefully close the connection (like quit-command in FTP-protocol), so 
tomcat knows, that everything is OK.

i know, that apache kills and spawns new child every now and than, but 
as this is normal, this should be handled more gracefully.

i cannot supply you with a patch, because i'm not that good in writing 
apache-modules (in fact, i never did that before, and i didn't write any 
C/C++ for some years now)


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org