DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36281>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36281 ------- Additional Comments From [EMAIL PROTECTED] 2005-08-19 21:33 ------- I would like to see your workers.properties and the Jk directives in your httpd configuration. Also: Could you please check, if the failing Apache child processes are still there, or if they died? The log chows the PID of the relevant process directly behind the date. If the process is still there, you can use /usr/proc/bin/pstack PID to write a thrad dump. That way we can confirm, in which function the hanging process sits. You could attach the pstack. If the process is not there any more, it might have crashed. In case you succeed in dumping a core file of the process, you can again use pstack on that core file. Finally it might be interesting to use truss (or if you are already familiar with it dtrace) to find out, if the error is related to some system call. Configure apache to only use very few children (like startng 2 servers and having sparemax and min also equals to 2). Start the server via truss -f -o some_output_file -w all -r all -v all \ /usr/local/apache/bin/apachectl start and then redo your tests (apache will be a little slow). The file some_output_file contains information about all system calls, about bytes read and written, signals received, errnos etc. To have a somewhat easier test case: In the log you attached one can see, that the working request for the html produces to image requests going to two apache processes in parallel which both fail. I ould be a simpler retest to only use single requests, not something in parallel, e.g. not automatically reloading embedded objevcts via the browser. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
