camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Rocca (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10146) Groovy language in route and no camel-groovy leads to memory leaks
Date Tue, 19 Jul 2016 10:58:20 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383946#comment-15383946
] 

Stefano Rocca commented on CAMEL-10146:
---------------------------------------

Hi Claus,
I think that, to really solve this issue, this page

http://camel.apache.org/groovy.html

should be updated: the last paragraph should mention camel-groovy and not camel-script.
Furthermore the support for groovy should be removed from camel-script because of groovy's
java scripting api implementation.

> 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, camel-script
>    Affects Versions: 2.15.5, 2.17.2
>            Reporter: Stefano Rocca
>            Assignee: Claus Ibsen
>
> Consider this simple route:
> <route id="leak">
> 	<from uri="file:///c:/temp/leak/in?move=.done&amp;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)

Mime
View raw message