Do you use SSL? We had this problem here and the problem was on Apache. It 
was corrected on apache 2.0.56. Look at the changelog: 
(http://www.apache.org/dist/httpd/CHANGES_2.0)
mod_proxy_http: Prevent data corruption of POST request bodies when
     client accesses proxied resources with SSL. PR 37145.
     [Ruediger Pluem, William Rowe] 

Rafael Sarres de Almeida
Seção de Gerenciamento de Rede
Superior Tribunal de Justiça
Tel: (61) 3319-9342





"James Grady" <[EMAIL PROTECTED]> 
18/09/2006 13:55
Favor responder a
"Tomcat Users List" <users@tomcat.apache.org>


Para
"Tomcat Users List" <users@tomcat.apache.org>
cc

Assunto
Re: Large Data Post Problem






Rainer,
   I tried upgrading mod_jk, but that did not solve the 
problem.  And, I double-checked that I did not have a 
small maxPostSize value set anywhere.
   Initially I suspected that I might have a bad encoded 
value in my uploaded data, but if I split the 40k data set 
into 2 pieces it will upload with no problems.  I believe 
this means that there probably isn't incorrectly encoded 
data.
   I'll keep looking and will respond again if I an find 
the problem.
   Thanks for the help.
 
James

On Sat, 16 Sep 2006 17:44:23 +0200
  Rainer Jung <[EMAIL PROTECTED]> wrote:
> I tried with mod_jk 1.2.18 and Apache 2.0.58. No 
>problems, this should
> work. Although I doubt it's a problem in the mod_jk 
>version, maybe you
> should upgrade.
> 
> Did you set maxPostSize on the tomcat connector to some 
>small size? The
> default is 2MB.
> 
> Regards,
> 
> Rainer
> 
> James Grady schrieb:
>> I am running Apache 2.0.48 that uses mod_jk 1.2.10 to 
>>communicate with
>> Tomcat 5.5.7.  When my client posts large requests 
>>(about 40K) to
>> Apache, I can see where the request is sent through 
>>mod_jk, but when it
>> gets to Tomcat the data has a length of zero.
>> 
>> Is there a way to increase the amount of data that can 
>>be passed through
>> mod_jk without failure?
>> 
>> My mod_jk log file has this data in it when the data is 
>>lost:
>> 
>> 
>> 
>> [Fri Sep 15 16:03:46 2006] [1391:60336] [debug]
>> ajp_send_request::jk_ajp_common.c (1240): request body 
>>to send 40654 -
>> request body to resend 0
>> [Fri Sep 15 16:03:46 2006] [1391:60336] [trace]
>> ajp_read_into_msg_buff::jk_ajp_common.c (1093): enter
>> [Fri Sep 15 16:03:46 2006] [1391:60336] [trace]
>> ajp_read_fully_from_server::jk_ajp_common.c (1047): 
>>enter
>> [Fri Sep 15 16:03:46 2006] [1391:60336] [trace]
>> ajp_read_into_msg_buff::jk_ajp_common.c (1129): exit
>> [Fri Sep 15 16:03:46 2006] [1391:60336] [trace]
>> ajp_connection_tcp_send_message::jk_ajp_common.c (894): 
>>enter
>> [Fri Sep 15 16:03:46 2006] [1391:60336] [debug]
>> ajp_connection_tcp_send_message::jk_ajp_common.c (898): 
>>sending to ajp13
>> pos
>> =4 len=8192 max=8192
>> [Fri Sep 15 16:03:46 2006] [1391:60336] [debug]
>> ajp_connection_tcp_send_message::jk_ajp_common.c (898): 
>>0000    12 34 1F FC
>> 1F FA 44 61 74 61 3D 30 36 2D 30 30  - .4....Data=06-00
>> 
>> Thanks...
>> 
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: 
>>[EMAIL PROTECTED]
>> For additional commands, e-mail: 
>>[EMAIL PROTECTED]
>> 
> 
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: 
>[EMAIL PROTECTED]
>For additional commands, e-mail: 
>[EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to