I've published web service endpoint on Sun light weight http server. The server is running with ThreadPool executors for the connection (Executors.newCachedThreadPool()).
I'm also using regular web service client (also JAX-WS).
It seems that for every call that exceed 5 minutes the server (or the client) ends the current call thread and open a new one. In the server it looks like a new connection was established and trying to run the same action.
This only happens once, meaning the "second call" might exceed 5 minutes.
Is there a default timeout for a connection ? Is there a way to configure it ?
With the light weight http server, a connection would become idle after 5 mn. The implementation (have a look at ServerImpl and ServerConfig) closes the idle connections and there is currently no public property to set this idle timeout. If you want this kind of control, you may want to use a servlet container. Or you could use Jetty (which provides a SPI) instead of Sun default HttpServer.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With