Description
Hello!
Using the HTTP transport, I've noticed a few things
- It seems that for large message consumption, the InactivityMonitor will kick in after the 30 second default, even if a message is in the process of being downloaded.
- The HTTP InactivityMonitor timeout is not configurable. I've worked around that temporarily by modifying DEFAULT_CHECK_TIMEOUT_MILLS in AbstractInactivityMonitor.java and updating it to take a Java system property, but it would be idea if it were configurable similar to how it is for the TCP transport
Thanks in advance for your consideration of this feature request!