cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhawal (JIRA)" <>
Subject [jira] [Commented] (CXF-7246) PhaseInterceptorChain's Message is not passed to child threads.
Date Wed, 29 Mar 2017 12:34:41 GMT


Dhawal commented on CXF-7246:

Hi Daniel,

I din't get the point of Memory leaks over here. In case i am having a doubt here, since the
executors are properly shut down before the response to servlet thread is fed back. Your point
of memory leak is valid if we are having an asynchronous execution where servlet thread is
not held up. 

Anyways thanks for pointing it out. We have a fix in place for manually copying the context.


> PhaseInterceptorChain's Message is not passed to child threads. 
> ----------------------------------------------------------------
>                 Key: CXF-7246
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.6.14
>            Reporter: Dhawal
>             Fix For: Invalid
> 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
> 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
> Thanks,
> Dhawal Patel

This message was sent by Atlassian JIRA

View raw message