You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Stefano Rocca (JIRA)" <ji...@apache.org> on 2016/07/18 07:54:20 UTC
[jira] [Updated] (CAMEL-10146) Groovy language in route and no
camel-groovy leads to memory leaks
[ https://issues.apache.org/jira/browse/CAMEL-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefano Rocca updated CAMEL-10146:
----------------------------------
Affects Version/s: 2.17.2
> Groovy language in route and no camel-groovy leads to memory leaks
> ------------------------------------------------------------------
>
> Key: CAMEL-10146
> URL: https://issues.apache.org/jira/browse/CAMEL-10146
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.15.5, 2.17.2
> Reporter: Stefano Rocca
>
> Consider this simple route:
> <route id="leak">
> <from uri="file:///c:/temp/leak/in?move=.done&moveFailed=.error"/>
> <setHeader headerName="dummy"><groovy>"dummy" + System.currentTimeMillis()</groovy></setHeader>
> <to uri="file:///c:/temp/leak/out"/>
> </route>
> each time I put a file in c:/temp/leak/in, the number of instances of org.codehaus.groovy.control.CompilerConfiguration increases by one.
> Since each CompilerConfiguration, because of this other issue GROOVY-7884, is created anew and contains a BufferedWriter which in turn contains two buffers of 8192 elements (one char[8192] and one byte[8192]), the heap is soon consumed by useless buffers...
> Including camel-groovy in the dependencies the problem disappears.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)