Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
MIME-Version: 1.0
In-Reply-To: <1495021160823-5799704.post@n5.nabble.com>
References: <1494911280419-5799551.post@n5.nabble.com> <CAGB5yNmJd5tQ52m09=Cn=yV0yn3U4-jC4Jqqi393ixyq_3W9Rg@mail.gmail.com>
 <1495021160823-5799704.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 17 May 2017 15:51:38 +0200
Message-ID: <CAGB5yN=zK3Vn4nw7DCT64HjrH+QAzPNf8m73zNPLh3q-VSEbdw@mail.gmail.com>
Subject: Re: Redelivery of message in case of exception inside aggregator
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset="UTF-8"
archived-at: Wed, 17 May 2017 13:52:10 -0000

I suggest to use a profiler to see what is going on in your JVM.

You may need to tweak restlet accordingly to your needs. You can set
limits on thread pools and whatnot.

And maybe also the load on the JVM if you have a lot of messages queued up etc.

Camel has little overhead, so its often other things you need to tweak.
However as you use SEDA with an unbounded queue you can end up with
too many messages pending, if you take in more messages than you can
process.


On Wed, May 17, 2017 at 1:39 PM, codentravel <shivaprashanthn@gmail.com> wrote:
> Thanks for the reply.
> I did exactly the same yesterday.. It seem to be working fine..
>
> Do you have any suggestion bring the CPU down ?
>  Currently it consumes about 70% of CPU (beaglebone with 1gb of RAM) for 15
> messages/second.  Is it normal for Camel to consume so much of CPU ?
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Redelivery-of-message-in-case-of-exception-inside-aggregator-tp5799551p5799704.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2