Connection interrupted on the server due to client timeout.

[brunoczo]

I have an application using WebFlux that processes a large amount (~500 TPS) of transactional information. The application runs two services: when the first service succeeds, it triggers a call to the second one. However, the second service, which uses reactive programming and runs on Netty, can be slow in some cases. To provide a quick response to the client, we have set a 2-second timeout on the requesting application, and the client checks the result through another service.

The problem is that when a timeout occurs, the second service stops execution without completing, even though it handles transactional information. Is it possible to ensure that the request is not interrupted if the client has a short timeout?

[yawkat]

Netty does not explicitly cancel running code when the client closes a connection (though e.g. write futures may fail). Sounds more like a thing webflux would do

[violetagg]

It depends on what kind of reactive pipeline you build. I would encourage you to ask Spring/Reactor maintainers.

[brunoczo]

Thank you for your response. But how does the TimeoutHandler work in Netty? The documentation shows that if no data is received for 30 seconds, the channel is closed.

[violetagg]

Do you use timeout API provided by Reactor Netty or Reactor or you extend the pipeline with your own timeout ChannelHandler?