I'm using apache2-2.0.54 on Debian. I have a website where for some unexplained reason web request **sometimes**, for a few users, take up to 30 seconds, whereas they should take <5. After some research, i found the delay was not on the application server(J2EE), so i figured it's probably on the apache proxy or some sort of networking issue. One thing i seem to have isolated is we use a 3rd party apache module (tealeaf) on the proxy, and i have deducted it might be the culprit. This module job is to had some request identification cookies to the request. Anyhow, i don't have the sources of the module, and there doesn't seem to be any useful tracing/logging options to it that could tell me how long it takes for the module to do it's job, so that is where my question comes in: ---------- **The actual question** ------- Is there a way to trace how long a module takes to do is task (without changing the module) ? maybe an apache option or add-on? or maybe i can easily write some sort of "wrapper" for the module, that would just time it (would that have to be C code or could i call a script. say Perl or bash etc...)? anybody as such a script ? ---------- Any help on this would be greatly appreciated. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|