[jira] [Comment Edited] (AMQ-9103) Make HTTP InactivityMonitor timout configurable

["Jean-Baptiste Onofré (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-9103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690709#comment-17690709 ] 

Jean-Baptiste Onofré edited comment on AMQ-9103 at 3/13/23 12:51 PM:
---------------------------------------------------------------------

As this is a change, I will do that for 5.19.0.


was (Author: jbonofre):
As this is a change, I will do that for 5.18.0.

> Make HTTP InactivityMonitor timout configurable
> -----------------------------------------------
>
>                 Key: AMQ-9103
>                 URL: https://issues.apache.org/jira/browse/AMQ-9103
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 5.17.2
>            Reporter: Chris Lenderman
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 5.19.0
>
>
> 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|https://github.com/apache/activemq/blob/189a2755a583928af2c71b74e08aa8d52c1d12ef/activemq-client/src/main/java/org/apache/activemq/transport/AbstractInactivityMonitor.java#L49] 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|https://activemq.apache.org/tcp-transport-reference]
> Thanks in advance for your consideration of this feature request!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)