The Camel route is complex, but it is looking good.
If the performance test result meets your need, I don't the questions
those you ask will hit you in the production environment.
On Mon Nov 28 18:33:32 2011, Omar Atia wrote:
Dears,
Kindly find attached Camel-context.xml Please let me know , the old e-mail
attachment is the input XML to Mina route.
Thanks,
Omar Atia
-----Original Message-----
From: Willem Jiang [mailto:willem.ji...@gmail.com]
Sent: Monday, November 28, 2011 3:02 AM
To: users@camel.apache.org
Subject: Re: Configuration for Apache camel...
I don't think you attached a right camel route as there is only a cxf
endpoint and no camel-mina endpoint.
BTW, if the POJO data format can meet your need, you don't need to
change any thing :)
On Sun Nov 27 16:34:14 2011, Omar Atia wrote:
Dear Willem,
Kindly find attached XML Used to create Subscriber on IN , this XML will be fed
into Camel route , that listens to tcp-mina port .
I'm doing spring configuration and using POJO format in order to fed the XML
directly after JAXB into the WS .
The question , you mentioned below that you can send the request direct to
backend WS service how ?
For performance testing , we just tried sending 100,000 request daily and it
goes fine while monitoring through Jconsole .
Thanks,
Omar Atia
-----Original Message-----
From: Willem Jiang [mailto:willem.ji...@gmail.com]
Sent: Sunday, November 27, 2011 5:43 AM
To: users@camel.apache.org
Subject: Re: Configuration for Apache camel...
Did you have a chance to do some performance test ?
What's your XML String looks like ? If there are not much change on the
XML, you can send the request direct to back end WS service.
We could do some enhancement according to your requirement.
On Sat Nov 26 16:07:12 2011, Omar Atia wrote:
Just to assume that Mina tcp endpoint will receive maximum 1500 Byte as XML
string per trx in synchronous mode ...can this be dangerous ...
Sent via BlackBerry® from mtc touch
-----Original Message-----
From: Björn Bength<bjorn.ben...@gmail.com>
Date: Sat, 26 Nov 2011 00:54:39
To:<users@camel.apache.org>
Reply-To:<users@camel.apache.org>
Subject: Re: Configuration for Apache camel...
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<omar.a...@its.ws> 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.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
