[
https://issues.apache.org/jira/browse/CAMEL-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012118#comment-13012118
]
Claus Ibsen edited comment on CAMEL-3813 at 3/28/11 4:10 PM:
-------------------------------------------------------------
Thats was actually by design. But maybe there is a need to ensure the thread
locals is cleared when the exchange is done.
was (Author: davsclaus):
Thats by design
> 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: Bug
> Components: camel-core
> Affects Versions: 2.7.0
> Reporter: Marcin Kolda
> Labels: xpath
>
> 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
