[
https://issues.apache.org/jira/browse/CAMEL-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012526#comment-13012526
]
Claus Ibsen commented on CAMEL-3813:
------------------------------------
Your unit test is flawed as it doesn't handle the unit of work which will
ensure the thread locals get cleared when the exchange is done being processed.
So check out a Camel route instead, and check in your system for real.
> XPathBuilder doesn't clear ThreadLocal with exchange after evaluation
> ---------------------------------------------------------------------
>
> Key: CAMEL-3813
> URL: https://issues.apache.org/jira/browse/CAMEL-3813
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.7.0
> Reporter: Marcin Kolda
> Priority: Minor
> Labels: xpath
> Fix For: 2.8.0
>
> Attachments: bug_reproduction.patch
>
>
> XPathBuilder doesn't clear ThreadLocal with exchange (and variableResolver)
> after evaluation. In such case reference to current exchange (and body,
> headers, properties, etc.) remains in Thread until current thread dies or
> evaluates new exchange with the same XPathBuilder instance.
> The result of this is that each thread can contain references to multiple
> exchanges (up to the number of xpaths in camel context), that can't be
> collected by GC.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
