aspose file tools*
The moose likes Other Java Products and Servers and the fly likes Timeout configuration in Apache Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » Other Java Products and Servers
Bookmark "Timeout configuration in Apache" Watch "Timeout configuration in Apache" New topic
Author

Timeout configuration in Apache

Abilash Vs
Greenhorn

Joined: Mar 12, 2012
Posts: 5
Hello folks,

I am using apache 2.2 version and I have three servers configured there for load balancing purpose (like as below)

BalancerMember http://node1:port/ route=node1
BalancerMember xxxx://node2:xxxx/ route=node2
BalancerMember xxxx://node3:xxxx/ route=node3

However the backend application nodes configured in balancer member requires lot of processing time and hence we were facing issues related to timeout like as below

“The timeout specified has expired: proxy: error reading status line from remote server ”

As I had a customised .conf file ,I had to add the below lines explicitly to avoid picking default timeout value from default http-default.conf file

<VirtualHost server:port>
Timeout 500
<Proxy balancer://xxxxx>;
BalancerMember http://node1:port/ route=node1 timeout=500
</Proxy>
</VirtualHost>

So now my questions are:

Do I need to explicitly configure timeout value at both the levels as shown above,
a) Timeout 500 outside Proxy.

b) timeout=500 at BalancerMember level.

I came across somewhere that if the timeout of the Apache BalancerMember is not configured the global Apache timout is inherited there. Please suggest..

Also please suggest the exact parameters in apache that needs to be tuned when huge concurrent requests are anticipated ?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Timeout configuration in Apache