Hello all, Thanks to everyone for your suggestions, investigations, etc. especially to Christoph Zwerschke, who discovered what turned out to be the cause of the problem.
Don't use os.chdir() in a threaded environment. I apologize to everyone if this is common knowledge, but it's news to me. At Chris' suggestion, removing the chdir calls in the two modules fixes the problem, and everything works as expected. Thanks again, -Gary On Sep 7, 2006, at 1:16 PM, Gary Perez wrote: > Hello all, > > I've searched through all the past mailing list archives & scoured > the web looking for an idea as to what's going on. Sorry this is so > long, just trying to cover all my bases. > > First, the setup: CentOS release 4.3 (Final) running Apache 2.0.52 in > front of Webware 0.9.1 via mod_webkit(2). Standard httpd > configuration, with: > > LoadModule webkit_module modules/mod_webkit.so > <Location /dyn> > WKServer 127.0.0.1 8086 > SetHandler webkit-handler > </Location> > > All the other WebKit apps run as expected. > > Here's my problem, and I hope you can help. > > 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? > > Thanks in advance for any light you can shed on this 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
