You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Steffen Rumpf (JIRA)" <ji...@apache.org> on 2008/10/13 16:18:52 UTC
[jira] Created: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
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.2, 3.2.1
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.
[jira] Updated: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steffen Rumpf updated SM-1631:
------------------------------
Priority: Major (was: Blocker)
> 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
> 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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46409#action_46409 ]
Guillaume Nodet commented on SM-1631:
-------------------------------------
I've just done a quick analysis using a memory profile and found the following:
{code}
char[5144574] 10,289,160
value of java.lang.StringBuffer 16
buf of java.io.StringWriter 24
m_writer of org.apache.xml.serializer.ToXMLStream 128
m_serializer of org.apache.xalan.transformer.TransformerIdentityImpl 64
fLexicalHandler of org.apache.xerces.parsers.SAXParser 88
value of java.lang.ThreadLocal$ThreadLocalMap$Entry 32
[13] of java.lang.ThreadLocal$ThreadLocalMap$Entry[17] 80
table of java.lang.ThreadLocal$ThreadLocalMap 24
threadLocals of java.lang.Thread [Stack Local, Thread] 96
{code}
I don't think these objects are actually leaking and they are stored in a thread-local and should be reused across invocations. However, they eat a lot of memory and we might want to ensure that they are released and garbaged if possible. I don't have any allocation information to track where these objects are allocated from so I'm not sure we can do anything about those right now.
Anyway, I think we should lower the priority of this issue as this is not a memory leak i think.
Btw, if you shut down the EIP component, you'll see the memory decrease to its original value.
> 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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46499#action_46499 ]
Steffen Rumpf commented on SM-1631:
-----------------------------------
maybe this is related to https://issues.apache.org/activemq/browse/SM-1560
> 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
> 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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46500#action_46500 ]
Steffen Rumpf commented on SM-1631:
-----------------------------------
does not solve my problem!
> 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
> 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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46428#action_46428 ]
Steffen Rumpf commented on SM-1631:
-----------------------------------
Ok, I will test both. On the issue with xalan a patch is created I will apply it and build new jars of xalan-2.7.0 I will report if it works and provide you with the fixed packages. Otherwise I will try ur other workaround.
> 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-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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46435#action_46435 ]
Steffen Rumpf commented on SM-1631:
-----------------------------------
1. Patching xalan only solves a half of this issue, so there must be another point which consumes heap. If I patch xalan the data staying in heap is reduced to 150 Mbytes, but not totaly released.
2. With the settings you provided I got no change.
> 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-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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46411#action_46411 ]
Guillaume Nodet commented on SM-1631:
-------------------------------------
I don't think you won't. I think these objects are reused or erased on the next use of the thread. I also think these objects won't be released until the xml parser is reused from this thread, or the thread dies which should happen a few minutes later depending on the threadpool parameters.
You should test it with a small and continuous load (for example, put a file in the input box every second) and see what it gives on the long run, but i doubt there will be any memory 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, 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.
[jira] Updated: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steffen Rumpf updated SM-1631:
------------------------------
Attachment: servicemix-memory-leak.png
Memory leak after processing 4 exchanges
> 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, 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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46410#action_46410 ]
Steffen Rumpf commented on SM-1631:
-----------------------------------
Hm, ok but the problem for me is that if I don't get the memory free I will fast run into trouble. So what can I do or how long will it normaly take that this objects are released?
> 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.
[jira] Updated: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steffen Rumpf updated SM-1631:
------------------------------
Attachment: servicemix-memory-leak.zip
New testcase.
> 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, 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.
[jira] Updated: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steffen Rumpf updated SM-1631:
------------------------------
Fix Version/s: (was: 3.2.1)
(was: 3.2.2)
> 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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46436#action_46436 ]
Guillaume Nodet commented on SM-1631:
-------------------------------------
I've tested my workaround and it seems to work as long as you give a few minutes for the thread to die (you can check with jconsole). Then if you perform a garbage collection, the heap goes down.
> 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-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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46451#action_46451 ]
Steffen Rumpf commented on SM-1631:
-----------------------------------
I'm working on it just a moment.
> 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-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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46425#action_46425 ]
Guillaume Nodet commented on SM-1631:
-------------------------------------
I think you just hit the following issue: https://issues.apache.org/jira/browse/XALANJ-2195
Not sure if there is any work around.
> 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-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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46412#action_46412 ]
Steffen Rumpf commented on SM-1631:
-----------------------------------
This is what I've really done look at the second screenshot I've added (ok I've used a bigger file). But even I waited after one run a longer (time about an hour) and nothing happend. So for me it seems that this objects are not reused and not be cleaned up after time.
> 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.
[jira] Updated: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steffen Rumpf updated SM-1631:
------------------------------
Attachment: LongRun.png
Over night I've tested if the memory is released after processing a huge message. But you can see that this does not happen after 10 hours.
> 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-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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46450#action_46450 ]
Guillaume Nodet commented on SM-1631:
-------------------------------------
I guess there is a different issue involved there. Do you have a test case ?
> 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-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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46426#action_46426 ]
Guillaume Nodet commented on SM-1631:
-------------------------------------
Well, I guess one workaround would be to make sure the threads are released.
This can be done by changing the values in [install]/conf/servicemix.properties to the following values:
{code}
servicemix.corePoolSize = 0
servicemix.maximumPoolSize = 32
servicemix.queueSize = 0
{code}
After 60 seconds, all unused threads will die so the references to the SAXParsers will go away and the GC can reclaim the used memory.
> 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-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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46449#action_46449 ]
Steffen Rumpf commented on SM-1631:
-----------------------------------
For me its a little bit strange. Processing my bean direclty: works. Sending message to multiple files using eip: works. Sending multiple messages to file and bean using eip: Don't works.
> 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-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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "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.
[jira] Commented: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (SM-1631) Memory leak while using eip component
(wiretab, static recipient)
Posted by "Steffen Rumpf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steffen Rumpf updated SM-1631:
------------------------------
Attachment: servicemix-bean-test2.zip
servicemix-bean-test2.zip
> 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.