Symptom:
After processing requests for several days, Federation Manager's built-in proxy engine hangs.
Solution:
Modify tuning parameters in the proxy engine's server.conf for the connection between Apache web server (HTTP listener) and the proxy engine (Tomcat servlet engine).
The parameters you modify are used by the component mod_jk, which acts as the Tomcat connector to enable communication between the Apache web server and Tomcat using the Apache JServ protocol (AJP).
To modify the server.conf file
federation_mgr_home/secure-proxy/proxy-engine/conf
Specifies the maximum time, in milliseconds, that can elapse between any two packets received from the proxy engine. After this timeout expires, the connection between the Apache server (HTTP listener) and the proxy engine is dropped. A value of 0 indicates that the proxy engine will wait indefinitely until a response is received.
To ensure that the connection does not wait indefinitely for a response from the proxy engine, increase this value.
Default: 0
Indicates the maximum number of times that the mod_jk component sends a connection request to the proxy engine in case of a communication error. After the number of retries has been met and there is no response from the proxy engine, the connection is dropped.
Increase this value for more retry attempts for a connection request.
Default: 2
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |