[
https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46414#action_46414
]
Steffen Rumpf commented on SM-1631:
-----------------------------------
Ok for very small files < 1 Mbyte you are right. Its not possible to get the
heap crowing up (tested with ca. 150 exchanges). But directly if I use larger
files about 2 Mbyte I need not much exchanges to grow up the heap and it takes
a very long that this released again (currently I am waiting for about 30
minutes without a change in my heap). I will try over night if the heap is
released (for my project start I think this is ok but later it could be that I
have more traffic to handle).
> Memory leak while using eip component (wiretab, static recipient)
> -----------------------------------------------------------------
>
> Key: SM-1631
> URL: https://issues.apache.org/activemq/browse/SM-1631
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: servicemix-eip-2008.01
> Reporter: Steffen Rumpf
> Priority: Blocker
> Attachments: FileToThreeFiles.png, servicemix-bean-test.zip,
> servicemix-memory-leak.png, servicemix-memory-leak.zip
>
>
> I am using a eip-component (tested both static recipient and wiretab) and
> received a memory leak while processing messages. There is a simple testcase
> for this, when receiving a file and send it via eip to more then one file
> sender there is a remaining amount of heap which is not cleared by gc (even
> when I trigger the gc by hand).
> Related threads:
> http://www.nabble.com/Best-practices%2C-working-with-beans-and-huge-messages.-tt19914439ef12049.html
> http://www.nabble.com/Memory-issue-in-servicemix-tt19727632ef12049.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
