On Sep 8, 2006, at 8:34 AM, sophana wrote: > Looking at the error messages, it seems that it is webware that don't > accept the connection. > I don't know why, and don't even know if I have the same problem. > Are you sure that your second request is not blocked by the first > one in > webware?
How would I be able to determine whether the second request is being blocked? If the simple answer is "because the second request doesn't get served", then yeah, it's being blocked... but why, and is there a way around this? I admit I don't know a lot about threads/threading, but I was under the impression that the AppServer (as config'd below) could handle multiple, simultaneous requests. Is there something completely obvious that I'm overlooking? > Gary Perez a écrit : >> Hello all, >> >> [snip] >> >> I have two pages to be served *almost simultaneously* by WebKit: one >> of them is a large-file upload form processor which--naturally--will >> take a long time to return (a problem I will try to solve later), the >> second is a status page that lists the contents of a directory which >> self-refreshes once every three seconds. >> >> While the first is waiting for all the form-data to upload, the >> second simply does not respond, and eventually throws an Apache >> Internal Server Error (500). >> >> Apache error logs report ten of these: >> [Wed Sep 06 17:38:36 2006] [error] Can not open socket connection to >> WebKit AppServer >> [Wed Sep 06 17:38:36 2006] [error] Couldn't connect to AppServer, >> attempt 10 of 10, sleeping 1 second(s) >> ... and finally: >> [Wed Sep 06 17:38:37 2006] [error] timed out trying to connect to >> appserver -- giving up. >> >> I have WebKit's AppServer running threaded (default >> AppServer.config): >> StartServerThreads = 10 >> MaxServerThreads = 20 >> MinServerThreads = 5 >> >> Someone with greater knowledge of Apache stated: "The default mode >> for Apache 2 is pre-forking, aka, 1.3 compatibility." ... which I >> take to mean it forks child processes from the main control (root) >> process - and this is not the same thing as threading... am I >> mistaken in this assumption? >> >> Finally, is apache's inability to connect to the AppServer an >> inherent limitation and/or problem with the AppServer, *or* is it >> caused by running apache in pre-forking mode versus enabling threads >> there? If so, do you think that running both in threaded mode will >> resolve the problem? ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
