OneConnect not honoring connection KeepAlives by default
We're currently doing some testing on F5 LTM Virtual Edition 11.2.1 Build 1217.0 Hotfix HF9, and noticed that with the standard OneConnect profile enabled to our back-end nodes that connections weren't being kept alive. The back-end nodes are Tomcat 7 instances configured with a 300,000 ms keep-alive timeout and unlimited number of requests. Manual connections to the node keep-alive within the expected intervals. Connections from the F5 were immediately being closed via a FIN initiated from the F5 side to Tomcat.
After some experimentation, I found that the following iRule corrected the behavior:
when HTTP_REQUEST {
ONECONNECT::reuse enable
}
when HTTP_RESPONSE {
ONECONNECT::reuse enable
}
This seems to imply that "reuse" isn't the default per documentation (https://devcentral.f5.com/wiki/iRules.ONECONNECT-reuse.ashx). Has anyone else experienced this? Is it expected an iRule would be necessary to ensure server-side keep-alives function?