Thanks Keith.
I would not go to 3.3 for the time being. Is there a patch for 3.2.1?
Peter
-Original Message-
From: Keith Wannamaker [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 4:15 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem with mod_jk and ajp13
Hi Peter, this
it is possible.
Keith
-Original Message-
From: Peter Dai [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 7:56 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem with mod_jk and ajp13
Thanks Keith.
I would not go to 3.3 for the time being. Is there a patch for 3.2.1?
Peter
-Ori
:479)
-Original Message-
From: Dan Milstein [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 2:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Problem with mod_jk and ajp13
Peter,
There was a bug with POST size > 8K. This has been fixed in the 3.2 and 3.3
branches in cvs. I
Peter,
There was a bug with POST size > 8K. This has been fixed in the 3.2 and 3.3
branches in cvs. I am almost certain that it was fixed in the 3.2.1 release
available at:
http://jakarta.apache.org/site/binindex.html
If you are using the 3.2.1 release and are still seeing this problem, pleas
: [EMAIL PROTECTED]
Subject: RE: Problem with mod_jk and ajp13
Dan,
Thanks for the help. I changed to tomcat 3.2.1 and it worked for large size
POST with
parameters.
However, it still fails for POST with object, and here is the stack trace:
Thanks,
Peter
java.io.StreamCorruptedException: Caught
Hi There,
Has anyone seen this problem.
1) I hava been doing applet-servlet communication with both parameters and
object, it has been working nicely for any size(upto ~50K) of the request in
my application.
2) Then I tried mod_jk / ajp13. For small requests, it worked fine. But
for large