node-timeout is an attribute set via worker

node-timeout
Timeout (in seconds) for proxy connections to a node. That is the time mod_cluster will wait for the back-end response before returning error. That corresponds to timeout in the worker mod_proxy documentation. A value of -1 indicates no timeout. Note that mod_cluster always uses a cping/cpong before forwarding a request and the connectiontimeout value used by mod_cluster is the ping value.

Reproducing:

1. Set up EAP with undertow as proxy balancer
2. Start EAP node/worker with standalone-full-ha.xml config: ./bin/standalone.sh -c standalone-full-ha.xml
3. Set node-timeout to 10 on node/worker:

   /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=node-timeout, value=10)

   or

   /subsystem=modcluster/proxy=default:write-attribute(name=node-timeout, value=10)

4. Deploy app that uses Thread#sleep() to sleep for 15 seconds. The goal here is to simulate request processing which took too long - longer than node-timeout value.
5. Request sent via balancer to deployed app should return 50x HTTP code after 10 seconds, but is returning 200 after 15 seconds.