top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Slow performance in Apache after IDAM Integration?

+2 votes
304 views

We have a tomcat and apache server on same physical machine. After integration with IDAM, whenever user is accessing the link through IDAM application it is either very slow or not accessible. After Apache restart it start working but after 3-4 hours again same issue occurs.

Tried to do some tuning as follows but no luck.

Timeout 120 
KeepAlive Off 
MaxKeepAliveRequests 100 
KeepAliveTimeout 15 
posted Aug 19, 2014 by Arjuna

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes

We have:

Apache 2.2.3
CentOS 5.5 x86_64
Splunk 5.0.2

I only know the basics but Apache has been serving us very well with the below config and only after about a week did pages refresh very slowly, up to a minute to reload sometimes.

I tailed both httpd and splunkd logs and saw a consistent delay of 30s between proxy and origin server (both on same host) along with plenty of 304s, followed by what appeared to be some timeout and then slowly the 200s started coming back in.

A restart of httpd cleared up the issue. Im lost, please help. Could this be a caching problem?

0 votes

I have two handlers to be accessed. My motive is to use the second handler if the first handler returns DECLINED.

I have tried various combinations of SetHandler, AddHandler and AddType but none has worked as overriding takes place in all of these combinations.

Is there any method in Apache to use more than one handler without overriding?

0 votes

I started apache server which has worker as mpm in debug mode. I killed the process with kill -9 then it kills the process and stop debug. But when I am using kill -term PID then it is not killing process. Whereas kill -term PID is woking with prefork debug.Â
If I want to use kill -term PID in debug mode of worker then how to do that.

0 votes

I am a bit confused about the mod_rewrite documentation. It shows this rule to block hotlinking:

RewriteCond "%{HTTP_REFERER}" "!^$"
RewriteCond "%{HTTP_REFERER}" "!www.example.com" [NC]
RewriteRule ".(gif|jpg|png)$" "-" [F,NC]

however, I'd think a better rule would be:

RewriteCond "%{HTTP_REFERER}" "^$" [OR]
RewriteCond "%{HTTP_REFERER}" "!(www.)?example.com/.*$" [OR,NC]
RewriteRule ".(gif|jpg|png)$" "-" [F,NC]

if I want to block anyone manually typing in a link (no referer) + hotlinking (probably has a referer). Do i need the [OR] on the 1st
RewriteCond and not the 2nd one? It seems to work with OR on both conditions.

...