I know this post is getting pretty stale at this point, but I'm reading through old messages and thought I'd try to respond, given that you have asked this question more than once and never received an answer.
Client request timeout indicates how long the server will keep a new connection open waiting for a request from the client. This setting is the reason the server will close the connection if you telnet to the XDBC port and then don't type anything. I imagine certain types of network disruption or client termination could also cause this timeout to fire. I can't think of a situation where it would produce something you could distinguish from a network failure, but I also can't think of a situation where it could occur under normal operation. Keep alive timeout indicates how long the server will keep the connection open waiting for additional requests. Keep-alive can improve the performance of clients making rapid-fire requests to the server by re-using connections, but keep-alive can also reduce the capacity of a heavily loaded server by keeping idle connections open. Setting keep-alive to zero causes the connection to be closed immediately after servicing a single request. Since every normal request results in a keep-alive timeout, which occurs between processing of requests, this is not an exceptional condition. On Nov 9, 2009, at 12:30 PM, Paul M wrote: XDBC/XCC app server: request timeout The request socket recv timeout, in seconds. keep alive timeout The keep-alive socket recv timeout, in seconds. time limit The maximum number of seconds allowed to service a request. time limit is "how long an xqy call" will be allowed to run from what I have observed? But when would the other two timeouts trigger exceptions? _______________________________________________ General mailing list [email protected]<mailto:[email protected]> http://xqzone.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
