You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Dennis Kieselhorst (JIRA)" <ji...@apache.org> on 2018/01/22 20:43:00 UTC

[jira] [Resolved] (CXF-5919) Configuring thread names in Jetty transport

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

Dennis Kieselhorst resolved CXF-5919.
-------------------------------------
       Resolution: Fixed
         Assignee: Daniel Kulp
    Fix Version/s: 2.7.13
                   3.0.2

> Configuring thread names in Jetty transport
> -------------------------------------------
>
>                 Key: CXF-5919
>                 URL: https://issues.apache.org/jira/browse/CXF-5919
>             Project: CXF
>          Issue Type: Improvement
>          Components: Configuration, Transports
>    Affects Versions: 3.0.1
>            Reporter: Alexander Zobkov
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: 3.0.2, 2.7.13
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> It would be great to be able to configure name for threads used by HTTP Jetty transport. In current implementation of Jetty transport, threads that handle requests have names like "qtp-xxxxx". 
> When you have multiple CXF Jetty engines configured in the same JVM, thread names related to different CXF Jetty engines are not distinguishable and this complicates debugging via Jconsole/JStack or by inspecting log files. For example:
> "qtp4563453246-43 Selector0" prio=... tid=…
>  qtp1453691733-34 Selector0" prio=… tid=…
> It would be great to have some like:
> workorder_4563453246-43
> stockprice_1453691733-34
> it’s possible to implement by passing additional parameter to Jetty QueuedThreadPool in the same way as other threading parameters are passed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)