Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 10 Feb 2017 09:04:42 +0000 (UTC)
From: "Dhawal (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.13042003.1486717471000.46852.1486717482274@Atlassian.JIRA>
In-Reply-To: <JIRA.13042003.1486717471000@Atlassian.JIRA>
References: <JIRA.13042003.1486717471000@Atlassian.JIRA> <JIRA.13042003.1486717471530@jira-lw-us.apache.org>
Subject: [jira] [Created] (CXF-7246) PhaseInterceptorChain's Message is not
 passed to child threads.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 10 Feb 2017 09:04:49 -0000

Dhawal created CXF-7246:
---------------------------

             Summary: 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 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)