Hi Daniel, We used option#2 for the implementation of operation level timeouts at client side.
When we introduced this, we saw that the middleware (TIBCO) started failing to process the requests on the peak load and there are a lot of 503 errors. If we do the same performance test without this configuration and keep the timeout generic at the http conduit level then there is no impact on middleware. Is there any king of such issue in operation#2 which points towards the problem we are facing? Regards, Amit -- View this message in context: http://cxf.547215.n5.nabble.com/Webservice-Client-Receive-Timeout-options-HttpClientPolicy-setReceiveTimeout-VS-Interceptor-Message-t-tp5732557p5733315.html Sent from the cxf-user mailing list archive at Nabble.com.
