You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Mateusz Nowakowski (JIRA)" <ji...@apache.org> on 2014/01/09 12:41:50 UTC

[jira] [Updated] (CAMEL-7117) JettyHttpProducer.client._threadPool contains non-daemon threads only

     [ https://issues.apache.org/jira/browse/CAMEL-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mateusz Nowakowski updated CAMEL-7117:
--------------------------------------

    Summary: JettyHttpProducer.client._threadPool contains non-daemon threads only  (was: JettyHttpProducer.client._threadPool contains non-deamon threads only)

> JettyHttpProducer.client._threadPool contains non-daemon threads only
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-7117
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7117
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jetty
>    Affects Versions: 2.12.2
>         Environment: java7
>            Reporter: Mateusz Nowakowski
>             Fix For: 2.12.3, 2.13.0
>
>
> When custom JettyClient is created for JettyHttpProducer (line 79 invoking JettyClientComponent:708)
> only min/max threads can be provided, and all threads are created witn non-deamon flag.
> Personally I would make jetty client thread pool daemon only, but if it cannot be done, there should be additional flag on JettyEndpoint level to make it configurable.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)