Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A231811CDC for ; Thu, 10 Jul 2014 09:01:24 +0000 (UTC) Received: (qmail 65842 invoked by uid 500); 10 Jul 2014 09:01:24 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 65796 invoked by uid 500); 10 Jul 2014 09:01:24 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Delivered-To: moderator for users@camel.apache.org Received: (qmail 65275 invoked by uid 99); 10 Jul 2014 09:00:21 -0000 X-ASF-Spam-Status: No, hits=4.2 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Date: Thu, 10 Jul 2014 01:59:54 -0700 (PDT) From: a746076drdrb To: users@camel.apache.org Message-ID: <1404982794642-5753639.post@n5.nabble.com> Subject: Debugging Out Of Memory MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_87794_22417336.1404982794652" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_87794_22417336.1404982794652 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello,I've got OutOfMemory Exception and cannot find what causing the memory leak. The route itself downloads a file with 500 entries, splits it in streaming mode and for some filtered entries it downloads yet another file and puts it in a seda queue. In seda queue the message is processed while downloading 2-3 binary files associated with the message.It looks like camel does keep all exchanges in memory. Can someone please help me? I've attached screenshots of the heap dump. Thanks!The list of 20 biggest objects:Class Name Retained Sizejava.util.concurrent.LinkedBlockingQueue#11 148.779.172java.util.concurrent.LinkedBlockingQueue$Node#5741 148.655.127java.util.concurrent.LinkedBlockingQueue$Node#5771 148.655.095java.util.concurrent.LinkedBlockingQueue$Node#5772 148.522.267java.util.concurrent.LinkedBlockingQueue$Node#5841 148.389.627java.util.concurrent.LinkedBlockingQueue$Node#5842 148.256.697java.util.concurrent.LinkedBlockingQueue$Node#5845 148.123.869java.util.concurrent.LinkedBlockingQueue$Node#5843 147.990.983java.util.concurrent.LinkedBlockingQueue$Node#5844 147.858.097java.util.concurrent.LinkedBlockingQueue$Node#5846 147.725.269java.util.concurrent.LinkedBlockingQueue$Node#5847 147.592.321java.util.concurrent.LinkedBlockingQueue$Node#5873 147.459.681java.util.concurrent.LinkedBlockingQueue$Node#5893 147.326.853java.util.concurrent.LinkedBlockingQueue$Node#5915 147.193.867java.util.concurrent.LinkedBlockingQueue$Node#5916 147.060.861java.util.concurrent.LinkedBlockingQueue$Node#5917 146.928.035java.util.concurrent.LinkedBlockingQueue$Node#5918 146.795.127java.util.concurrent.LinkedBlockingQueue$Node#5919 146.661.839java.util.concurrent.LinkedBlockingQueue$Node#5933 146.529.011java.util.concurrent.LinkedBlockingQueue$Node#5934 146.396.185 heap_sorted_by_instances.PNG heap_sorted_by_retained.PNG heap_sorted_by_size.PNG heap_instances.PNG heap_instances_expanded1.PNG -- View this message in context: http://camel.465427.n5.nabble.com/Debugging-Out-Of-Memory-tp5753639.html Sent from the Camel - Users mailing list archive at Nabble.com. ------=_Part_87794_22417336.1404982794652--