I have a question regarding configuration of timeouts on a netty TCP server. Right now, I set the connect timout like this:
serverBootstrap.option(ChannelOption.CONNECT_TIMEOUT_MILLIS, 20000);
This seems to work, all good and well. Now I wonder if it's possible to define a "read timeout" on the server side. The idea would be that the server worker thread is interrupted when the read timeout elapses, so that it becomes available for other tasks. When I try to set the read timeout as follows I get an "unsupported channel option" warning at start-up:
serverBootstrap.childOption(ChannelOption.SO_TIMEOUT, 30000);
Is there a way to achieve a "read/processing timeout" on the server-side of things? Any help is appreciated.
Kind Regards, Michael