[
https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46466#action_46466
]
Steffen Rumpf commented on SM-1631:
-----------------------------------
After rethinking my yesterday work I came to the conclusion, that when we solve
this last issue, patching Xalan will work, so that we don't have to change the
SMX configuration. So that we have tow solutions:
- change the configuration of SMX
- patch Xalan that he releases its readers
Should I make a subtask for the remaining issue or do you have a solution for
that, so that we can close this issue.
> 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, LongRun.png,
> servicemix-bean-test.zip, servicemix-bean-test2.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.
