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

ASF GitHub Bot commented on CXF-5919:
-------------------------------------

GitHub user AlexanderZobkov opened a pull request:

    https://github.com/apache/cxf/pull/17

    Implementation of CXF-5919: Configuring thread names in Jetty transport

    This is implementation of CXF-5919. It passes threadNamePrefix attribute 
from Spring XML configuration to Jetty QueuedThreadPool setName method. 
Additionally, this pull request contains corresponding unit tests. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/AlexanderZobkov/cxf master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cxf/pull/17.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 #17
    
----
commit 4b2ae049adee7c068fe22f63ebd2dd44eeaae92d
Author: Alexander Zobkov <alexander.zob...@gmail.com>
Date:   2014-07-30T16:22:23Z

    Allow to configure the thread name prefix for threads that are used by the 
Jetty instance for processing requests

----


> 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
>            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 "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
(v6.2#6252)

Reply via email to