13, 2013 at 5:02 PM, Flavio Magacho - M4U
flavio.maga...@m4u.com.br wrote:
Hi,
I'm expecting some problems while running a load test on camel-netty
component.
** **
This is the route configuration:
route id=rtRead
from
uri=netty:tcp://pos-tcp
-feira, 20 de agosto de 2013 12:00
To: users@camel.apache.org
Subject: Re: Load test on camel-netty
I would suggest to remove the 100 thread pool sizes as the out of the box
settings from Netty is better. Netty is asynchronous and it creates thread
pools based on the number of CPU cores etc
-
From: Claus Ibsen [mailto:
claus.ibsen@
]
Sent: terça-feira, 20 de agosto de 2013 12:00
To:
users@.apache
Subject: Re: Load test on camel-netty
I would suggest to remove the 100 thread pool sizes as the out of the box
settings from Netty is better. Netty is asynchronous
2013 15:32
To: users@camel.apache.org
Subject: RE: Load test on camel-netty
If Oracle/Sun JDK is in use then maybe ask for a heap dump as the
OutOfMemoryError happens:
http://docs.oracle.com/cd/E15289_01/doc.40/e15062/optionxx.htm#BABBBEAJ
Then you could analyze the dump (e.g. using http
/ExecutionHandler.html
Babak
flavio.magacho wrote
Hi,
I'm expecting some problems while running a load test on camel-netty
component.
This is the route configuration:
route id=rtRead
from
uri=netty:tcp://pos-tcp-server.host:9000?decoder=#myDecoderamp;encoder=#myEncoderamp;sync
-
From: Babak Vahdat [mailto:babak.vah...@swissonline.ch]
Sent: quarta-feira, 14 de agosto de 2013 06:08
To: users@camel.apache.org
Subject: Re: Load test on camel-netty
Hi
The maximumPoolSize option is *actually* the value for the corePoolSize of the
ThreadPool being in charge, which is set
]
Sent: quarta-feira, 14 de agosto de 2013 06:08
To: users@camel.apache.org
Subject: Re: Load test on camel-netty
Hi
The maximumPoolSize option is *actually* the value for the corePoolSize
of the ThreadPool being in charge, which is set to 100 in your case (the
option naming seems a bit misleading
