Skip to content

When using Jetty, idle timeout for IO operations and delayed dispatch cannot be set to less than 30000ms #38960

@AElmecker

Description

@AElmecker

Encountered behaviour

After the upgrade to spring boot 3.2.0 or 3.2.1 (jetty 12) the HTTP connections always time out after 30000 ms, regardless of the value set through the server.jetty.connection-idle-timout property.

java.util.concurrent.TimeoutException: Idle timeout expired: 30004/30000 ms 

It seems that the timeout value was hardcoded during the upgrade to jetty 12 with this change.

Behaviour before upgrade

Previously (with spring-boot 3.1.5 in combination with jetty 11), no http idle timeout was set in the HttpConfiguration, so the default of jetty is to use the connection idle timeout, set via the property server.jetty.connection-idle-timout.

How to reproduce

If needed, I can provide an example and steps how to reproduce the issue.

Conclusion

Was this change intentional or an oversight?
Either way, imo this idle-timeout should be somehow configurable and not hard-coded.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: regressionA regression from a previous release

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions