Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <4029FC90.2070301@apache.org>
Date: Wed, 11 Feb 2004 10:57:36 +0100
From: Henri Gomez <hgomez@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.6b) Gecko/20031205 Thunderbird/0.4
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: failover-problem and
 session	mixup:	jakarta-tomcat-connectors/mod_jk:
 jk_ajp_common.c
References: <1075151098.1353.44.camel@centre.schwartz.local>
	 <4016993A.1080206@apache.org>
	 <1075928563.1340.28.camel@centre.schwartz.local>
	 <40220BCD.4070502@apache.org>
	 <1076010981.957.29.camel@centre.schwartz.local>
	 <40235B16.8040208@apache.org>
	 <1076364679.13266.1.camel@centre.schwartz.local>
	 <4028E0BD.7000000@apache.org>
 <4028ECBD.10200@apache.org>	 <4028F04B.5060203@apache.org>
 <1076445668.1180.20.camel@centre.schwartz.local>
In-Reply-To: <1076445668.1180.20.camel@centre.schwartz.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Alexander Schwartz a �crit :

> Am Di, den 10.02.2004 schrieb Henri Gomez um 15:52:
> 
> 
>>To fix this serious bug we should modify the current service API.
>>
>>We should store the POSTED datas in the jk_ws_service_t area and
>>not in ajp_operation_t, as such the first worker will feed the POST
>>datas in an area which will be available to the second one.
>>
>>Aternate idea are of course more than welcome;
> 
> 
> As I understand it mod_jk is "stable", almost "deprecated", and mod_jk2
> is "the future". Therefore I suggest: 
> 
>    * no API change in mod_jk
>    * mark the operation as unrecoverable when an error occurs after
>      the headers have been sent to the tomcat, that is only fixing
>      bugs and trying not to do big changes 
>    * concentrate your efforts on mod_jk2 and give people a reason to 
>      upgrade :)
> 
> Marking the operation as unrecoverable might also solve the other
> (lb-)problem: when you shut down the first tomcat after it has already
> sent some data to the client mod_jk forwards the request to the second
> tomcat and appends the response of the second tomcat to the response of
> the first tomcat. I'll deliver a sample jk.log soon. 

Ok, I commited changes in CVS which should fix problem in POST recovery.

Thanks to take a look at it

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