Very difficult to reproduce a situation under heavy load.
I stressed my Apache/TC with ab during nigths without
any failures but It was against simple servlets
-
Henri Gomez ___[_]____
EMAIL : [EMAIL PROTECTED] (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>-----Original Message-----
>From: Angel Aray [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, July 03, 2001 2:46 PM
>To: [EMAIL PROTECTED]
>Subject: RE: Ajp13 wrong Response
>
>
>
>I'll try that, but the problem I am seeing is with tomcat as late
>as TC 3.3-M3.
>
>-----Original Message-----
>From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
>Sent: Martes, 03 de Julio de 2001 04:10 a.m.
>To: [EMAIL PROTECTED]
>Subject: RE: Ajp13 wrong Response
>
>
>>> I am having a problem which is very difficult to reproduce.
>>Under certain
>>> conditions some request get the response for some other
>>request. It looks
>>> like at some point probably due to some synchronization
>issues tomcat
>>> mixes de responses from different clients.
>
>It was a known problem in early age of TC 3.3, with RequestDispatcher.
>Could you try a fresh install of TC 3.3-M4 ?
>
>>> I hadn't seen this behavior before, but since I moved from
>>using just
>>> tomcat to using apache + mod_jk + tomcat it has occurred a couple of
>>times.
>>>
>>> Has anyone seen this kind of behavior before?
>>>
>>>
>>> I am using apache_1.3.20, tomcat33-m3.
>>>
>>>
>>
>
