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]>
