In the application logs, a user was seen repeatedly logging into the application using an JDBC connection. This user id was making queries that pegged each of the 6 cpu's on this box. During this time, we could not correlate requests recorded in the apache access_log to these application activities. Further, the user who's account was making the requests was not logged in, and her PC was physically turned off.
One of the components of the web application seemed to be in a loop. Do any of you know apache well enough to comment on some of the timeout values that are configureable. I.E. Would apache re-submit a request to an application handler if it timed out? Could something like this go into a infinite loop? - I have my opinion, and our developers / dba's have theirs.
Some in directives in question are:
KeepAlive
KeepAliveTimeout
MaxKeepAliveRequests
Timeout
Thanks, I know application specifics are kind of vauge here, but that's the best I have.
-RYAN
--
Ryan Madison
Reno, NV 89521
e. [EMAIL PROTECTED]
aim. Alp1n1ste
yim. rhmadiso
_______________________________________________ RLUG mailing list [email protected] http://lists.rlug.org/mailman/listinfo/rlug
