Idle timeouts are necessary to prevent a server from waiting indefinitely for a request from a client, which unnecessarily ties up resources. When the timeout is exceeded, the server assumes that the client no longer needs the connection, possibly because of an error, and frees connection resources in an orderly fashion. This includes closing any connections to a server closer to the CV. Properly configured idle timeouts are particularly important for efficient connection pooling. The optimal length of the idle timeouts depends on the type of application or application server.
Note: Idle timeouts should generally be shorter the further away from the server they are set, to allow the servers to handle timeout errors more accurately and efficiently. Depending on how heavily loaded the servers are, the differences may be relatively large.
Idle timeouts can be specified for the application server's connection pool, the JDBC driver, the JDBC Server, and the CASERVER and IDMSJSRV tasks.
|
Copyright © 2009 CA.
All rights reserved.
|
|