[jira] [Commented] (AMQ-8039) Allow Inactivity monitor thread pool configuration

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on AMQ-8039:
------------------------------------------------------

Commit 0c986c33f6f4e6952fdad4ac5a4d040774b71955 in activemq's branch refs/heads/master from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=0c986c3 ]

AMQ-8039 - support system property configuration of the inactivity monitor thread pool, follow example of nio. new test to verify


> Allow Inactivity monitor thread pool configuration
> --------------------------------------------------
>
>                 Key: AMQ-8039
>                 URL: https://issues.apache.org/jira/browse/AMQ-8039
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 5.16.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 5.17.0
>
>
> In cases where there are lots of connections that timeout, there will be a one to one relation with the timeout task that stops the connection, this in turn fires an executor to close the underlying transport. 
> If any event of the stop blocks for a period there can be a large spike in inactivity monitor threads. Allowing inactivity monitor work to queue up in this case is sensible to place a bound on the number of threads in a broker process.
>  
> related: AMQ-4156 and AMQ-5480 AMQ-5486 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)