[jira] [Commented] (CXF-7246) PhaseInterceptorChain's Message is not passed to child threads.

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

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

Sergey Beryozkin commented on CXF-7246:
---------------------------------------

CXF 2.6.x is not supported now but have a look at 3.0.x or 3.1.x:

https://github.com/apache/cxf/blob/cxf-3.0.12/core/src/main/java/org/apache/cxf/interceptor/ServiceInvokerInterceptor.java#L91

as far as I recall it was done to avoid the locks when the custom executors are set but I wonder can something like that help in your case ?





> PhaseInterceptorChain's Message is not passed to child threads. 
> ----------------------------------------------------------------
>
>                 Key: CXF-7246
>                 URL: https://issues.apache.org/jira/browse/CXF-7246
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.6.14
>            Reporter: Dhawal
>
> Hello,
> We put few information(usually request header information) in Message through RequestHandler by doing PhaseInterceptorChain.getCurrentMessage.getExchange.put("","");  
> But when we create a new Threads from the thread which brings in request to the controller, those objects which are put in the Exchange are not available to new threads.  The PhaseInterceptorChain has Message object which is ThreadLocal so the objects are not available to subsequent threads which are created, so exploiting parallelism is quite painful once we store something in Exchange object. 
> As a suggestion can we have Message object as optional between ThreadLocal and InheritableThreadLocal and via a configuration we can set that do we need to make available Message object to child threads. 
> Thanks,
> Dhawal Patel



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)