I've been trying to test out mod_fcgid 2.2, and one particular url it consistently fails on. After running an overnight test I determined that the failed url fails after 40 seconds every time.
Yesterday I updated some parameters -- IdleScanInterval 120 BusyTimeout 300 BusyScanInterval 120 MaxProcessCount 20 MaxRequestsPerProcess 5000 IPCCommTimeout 300 IPCConnectTimeout 300 IdleTimeout 3600 ProcessLifeTime 7200 While trying to track this down, these parameters are in the global config, not in any virtual host config. However the failure still occurred. I looked at the source and saw this: #define DEFAULT_IPC_COMM_TIMEOUT 40 That's the only timeout that defaults to 40, so that must be the problem, I recompiled it with a default of 300 and am continuing the test, so far the url is responding within 27-29 seconds, so haven't reached the 40 second marker yet, but am wondering if this is a bug, or did I not use the parameter/my config is bad ? The same test/url under mod_fastcgi works fine. thanks nate ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mod-fcgid-users mailing list Mod-fcgid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mod-fcgid-users
