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 58C257084 for ; Fri, 25 Nov 2011 23:55:06 +0000 (UTC) Received: (qmail 26249 invoked by uid 500); 25 Nov 2011 23:55:05 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 26203 invoked by uid 500); 25 Nov 2011 23:55:05 -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 Received: (qmail 26195 invoked by uid 99); 25 Nov 2011 23:55:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Nov 2011 23:55:05 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bjorn.bength@gmail.com designates 74.125.82.51 as permitted sender) Received: from [74.125.82.51] (HELO mail-ww0-f51.google.com) (74.125.82.51) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Nov 2011 23:55:01 +0000 Received: by wwo28 with SMTP id 28so4428660wwo.20 for ; Fri, 25 Nov 2011 15:54:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XI2yDQO+EQtROSP9t+wjpC6JpgNuq2P24iHo2QVMadc=; b=J9/pIfbJshIC8YXxa0YvmCxIoRXbwxL2rft+ij5LhCT4IvWmbsOy00HJYedq5ittW/ NADBwZtRV6Ac2GL2+NqkTJvyIzfTncAaONiYnecLO24BHHJuovkO+/64CXXPJn9OkJy/ QdQTaqIFrotZX2kCp5d77R0Bxr3FiyXRh2gHs= MIME-Version: 1.0 Received: by 10.180.80.98 with SMTP id q2mr36218048wix.53.1322265279951; Fri, 25 Nov 2011 15:54:39 -0800 (PST) Received: by 10.216.171.69 with HTTP; Fri, 25 Nov 2011 15:54:39 -0800 (PST) In-Reply-To: <1322256843459-5023724.post@n5.nabble.com> References: <1322256843459-5023724.post@n5.nabble.com> Date: Sat, 26 Nov 2011 00:54:39 +0100 Message-ID: Subject: Re: Configuration for Apache camel... From: =?ISO-8859-1?Q?Bj=F6rn_Bength?= To: users@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, depends on what you do with your objects.. if all transaction payload are very, very large objects coming in at the same time and/or you store them in memory it will eventually leak yes. If you do normal sensible processing, and your load is spread out over the day, one million transactions a day is not too much at all. one million tx per hour should also be fine (from a camel perspective) if your hardware is not too old and your backend systems are up to it. you might need to add load balancing to another node at this stage depending on all aspects of your case. Regards B On Fri, Nov 25, 2011 at 10:34 PM, atiato wrote: > Dears , > I would like to know if there is special configuration for camel if we are > having heavy load , let us assume the following : > > 1- have Mina TCP endpoint . > 2- from TCP I use JAXB to transform XML coming into Object. > 3- call the Web service using CXF endpoint. > 4- convert response into Object . > 5- use JAXB to convert Object to XML . > 6- return that XML as response to TCP session. > > I have more than million transaction per day . > > How can I handle such load in apache camel taking into consideration high > availability with two sun server and load balancing assume WS response is > less than 1 second. > > Can this cause a memory leaks for example and use 100 % of memory . > > Can this consume all CPU and resources of the system . > > does this need to increase memory used for apache camel ? > > let us say we are having solaries sparc as hardware . > > I really appreciate your response . > > Thanks, > Omar Atia > > -- > View this message in context: http://camel.465427.n5.nabble.com/Configuration-for-Apache-camel-tp5023724p5023724.html > Sent from the Camel - Users mailing list archive at Nabble.com. >