Some of our web services run very long transactions (like generating a report that takes 60 min or multiples of that.)
Now we have encountered networks that use network gear (routers) with policies that cut any TCP connection that is open for 15 min and does not have any traffic (other than keep-alive). This means a connection over http times out, even if the http timeout is set to 0 (indefinite). My question is: Does the asynchronous Web service some active polling across the TCP connection to keep it alive? Is that the solution I'm looking for, Asynchronous invocation? P.S.: I looked at WS-Addressing too, but this seems to be for really cutting the client down and having some other transport for the response. Also, I'm stuck with CXF 2.0 for the moment and WS-A is only supported starting WS-2.1. -- View this message in context: http://www.nabble.com/Asynchronous-Invocation-and-connection-keep-alive-on-the-TCP-level-tp24835434p24835434.html Sent from the cxf-user mailing list archive at Nabble.com.
