----- Original Message ----- From: "Stephane Plante" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, July 10, 2002 1:50 PM Subject: RE: Problems With POST Method
> Thanks Emmett, > > Perhaps this is unrelated to the POST but triggered by something else? > > Has anyone ever seen that error before or can tell me what it means? > (jk_tcp_socket_recvfull) The short answer is that Tomcat dropped the connection before sending anything back to Apache. Most likely, this is a response to your error instead of the cause. > > Is there a mailing list that anyone can point me to in regards to mod_jk in > general? This is it :-). > > Thanks again, > > Stephane > > -----Original Message----- > From: Cunningham Emmett [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 10, 2002 3:23 PM > To: Tomcat Users List > Subject: Re: Problems With POST Method > > > > Just one datapoint. > > I haven't had any problems getting large datafiles > to upload using POST. I've been working with test > files in excess of 50MB. This is on Solaris 6 & 8, > NT, and Win2K running against Java 1.3.1_03 and > Tomcat 3.2.1. > > Though the most important aspect of this is the > upload servlet that you are using. I have not tried > Jeffery Hunters against huge datafiles, only single > digit MB sized ones. > > > --- Stephane Plante <[EMAIL PROTECTED]> wrote: > > Hi, > > > > After playing along happily for a while, our > > application ends up dying right > > at a POST. Tomcat ends up returning "bad fetch" in > > the logs when issuing > > this post. > > > > I am running: > > - Windows NT 4.0, SP 6a, IE 5.5 > > - Sun Java 2 SDK 1.4 > > - Tomcat 4.0.4 > > - Apache 1.3.24 > > - mod_jk.dll connector (only JSPs are being handled > > by Tomcat) > > > > I came across this error in "mod_jk.log": > > **** > > [jk_ajp13_worker.c (228)]: > > connection_tcp_get_message: Error - > > jk_tcp_socket_recvfull failed > > **** > > > > Could this mean that we are stuffing too much in a > > POST? Is there a fixed > > limitation imposed by Tomcat? Is there some > > buffer/parameter that we can > > increase, or any other measures that we can take > > that would allow us to get > > around this error? We are posting binary data, > > typically 50-60K in size. > > > > I have attempted to use Tomcat stand-alone, and the > > same error (bad fetch) > > still occurs (when we hit that POST in our > > application). > > > > This may be worthwhile to mention: our application > > works on JRun 3.1. (I > > don't intend on starting a flame war- but think this > > is useful enough to > > know.) > > > > I am still poking around, but any feedback would be > > greatly appreciated! > > > > Thanks in advance, > > > > Stephane > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > __________________________________________________ > Do You Yahoo!? > Sign up for SBC Yahoo! Dial - First Month Free > http://sbc.yahoo.com > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
