Hey Shawn, 2009/9/23 Shawn Yarbrough <[email protected]>: > I switched to mod_fastcgi. It helped. The UI is mostly responsive, but > erratic in that the "Loading" graphic greys out the page when I don't think > it should.
I haven't seen this before, many things could cause it : a crash, the apache server cannot respond to a request because all its threads are tied up, ... Can you be more specific of when you see what and perhaps make a test case that reproduces the problem ? > Is there any unusual effect from calling fork() from inside a Witty app's > event loop? Because to trigger a background job I call fork(), system(), > _exit() like I might in a regular C++ program. I must be doing something > wrong because I see this stuff in the Apache log: No that should be fine, nothing special about it... > FastCGI: incomplete headers (0 bytes) received from server > "/var/www/app/app.wt", referer: http://x.x.x.x:80/app/app.wt > (above message repeated ~30 times) This is an artefact of the server push. It is a known "non-issue" that we will fix in some future version. > FastCGI: invalid (dynamic) server > "/var/www/app/id/08YpuWHWY2kHnKku/index.html": access for server (uid 33, > gid 33) not allowed: execute not allowed by owner, referer: > http://x.x.x.x:80/app/app.wt > (above message repeated ~15 times) For some reason, your FastCGI thinks it needs to treat that file as a FastCGI server. This is caused by your FastCGI configuration ? Regards, koen ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
