You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/11 07:50:00 UTC
[jira] [Commented] (AMQ-7063) Be able to configure threading and
acceptor in HTTP Jetty transport connector
[ https://issues.apache.org/jira/browse/AMQ-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646074#comment-16646074 ]
ASF GitHub Bot commented on AMQ-7063:
-------------------------------------
GitHub user jbonofre opened a pull request:
https://github.com/apache/activemq/pull/307
[AMQ-7063] Be able to configure ActiveMQ http transport connector by providing a jetty.xml
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbonofre/activemq AMQ-7063
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq/pull/307.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #307
----
commit 68b33cadf7e9f10096e1ad16de6de4d4a2a4d14b
Author: Jean-Baptiste Onofré <jb...@...>
Date: 2018-10-11T07:18:32Z
[AMQ-7063] Be able to configure ActiveMQ http transport connector by providing a jetty.xml
----
> Be able to configure threading and acceptor in HTTP Jetty transport connector
> -----------------------------------------------------------------------------
>
> Key: AMQ-7063
> URL: https://issues.apache.org/jira/browse/AMQ-7063
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.14.3, 5.15.6
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.14.6, 5.16.0, 5.15.7
>
>
> Now, the {{http}} transport connector configures the Jetty connector in a "static" way (with a default set of configuration).
> When the {{http}} connector is "heavy" loaded, it would be helpful to be able to tune the Jetty connector, especially the acceptors, the min/max thread pool.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)