cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CXF-5919) Configuring thread names in Jetty transport
Date Tue, 12 Aug 2014 16:25:14 GMT


ASF GitHub Bot commented on CXF-5919:

Github user asfgit closed the pull request at:

> Configuring thread names in Jetty transport
> -------------------------------------------
>                 Key: CXF-5919
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>          Components: Configuration, Transports
>    Affects Versions: 3.0.1
>            Reporter: Alexander Zobkov
>            Priority: Minor
>   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
> 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

View raw message