Hi, try running your application with the JVM property camel.language.xpath.pre-compile set to false.
For example: mvn clean package && mvn exec:java -Dexec.mainClass="primeiro.app.camel.MainApp" -Dcamel.language.xpath.pre-compile=false Or the equivalent, using the launcher/script/runtime/etc for your application. Kind regards On Tue, Nov 9, 2021 at 11:42 AM Mikael Andersson Wigander < [email protected]> wrote: > Hi, thanks. creating a ticket now > > BTW: in the code the XPathBuilder only adds to the pool if the preCompile > flag is true. > How can I set this to false using @XPath() annotations and see if it > behaves different? > > > /M > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Tuesday, November 9th, 2021 at 10:11, Otavio Rodolfo Piske < > [email protected]> wrote: > > Unless you get an answer correcting me ... I'd say it looks like a bug. > > If you could create a ticket on Jira with a reproducer, I think we could > take a closer look. > > Kind regards > > On Tue, Nov 9, 2021 at 9:01 AM Mikael Andersson Wigander > <[email protected]> wrote: > >> Hi >> >> My last question came to this conclusion and therefor I create a new >> thread here. >> >> How and where should the XPathBuilder clear the pool it uses when adding >> @Xpath() expressions? >> There's a overridden method doStop() in it but I can't see where/when it >> is called. >> I tried to put a breakpoint on it in my sample but it was never called. >> >> In my previous problem I was left with orphaned data that the GC never >> cleared out and it looks like this is the leak. >> >> /M > > > > -- > Otavio R. Piske > http://orpiske.net > > > -- Otavio R. Piske http://orpiske.net
