http-listener read-timeout attribute implications

[Hao Chen]

After upgrading to wildfly 16 from JBoss EAP6, we are finding that requests to a rest service or MBean endpoint got dropped after 60s.  We don't see any error and it's just the connection got dropped. 

We tested and seems that the following settings can increase the timeout:

<http-listener name="default" socket-binding="http" ... read-timeout="1800000"

From the document on https://wildscribe.github.io/WildFly/16.0/subsystem/undertow/server/http-listener/index.html, it's not clear how exactly this attribute works --- we originally thought this for the server to read and upload... But apparently it's the server dropping client read connections. Can any body explain more about how this works and why the default behavior is very different from JBoss and the value is so small? -- quite some our services would take longer than 60s.

Thanks in advanced.

- Hao