[jira] Commented: (SM-1631) Memory leak while using eip component (wiretab, static recipient)

["Steffen Rumpf (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46404#action_46404 ] 

Steffen Rumpf commented on SM-1631:
-----------------------------------

Ok, I've teste a little bit and found out where this problem relates to. I've create a new testcase its only a file poller and a simple bean the bean is a MessageExchangeListener and only creates a copy of the NormalizedMessage of the exchange by using the MessageUtil.copyIn(MessageExchange) method and I got the memory leak again. So I think, when I look at the source of NormalizedMessageImpl and MessageUtil it must have something to do with the NormalizedMessageImpl class. I've attached the new testcase called servicemix-memory-leak and a screenshot of my jconsole called servicemix-memory-leak.png.

> 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
>             Fix For: 3.2.1, 3.2.2
>
>         Attachments: FileToThreeFiles.png, servicemix-bean-test.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.