Babak,
Below is the brief which may help you to understand my use case.
I have application which uses ActiveMQ (V 5.3.0) as MOM. We are using Camel
(V 2.7.2) to CONSUME messages from the MOM server.
One of the Module belongs to my application needs to register to camel with
7 unique subject for each incoming request. For e.g this module will
register 3500 unique subject to MOM server through camel for 500 incoming
request. As the subject are unique i cant make use of wildcard here.
In a real scenario, this module may need to serve up to 30000 such incoming
request. Hence the max registration may goes up to 210000.
Along whith the above module, I do have other module which also registers to
the MOM through the Camel API. But the number of subject registration is
less.
Hope now you got a clear understanding of my use case.
I have slightly modified my code (to make use of Spring
CachingConnectionFactory and JmsComponent) now and i am able to add upto
4000 in a single camel context.
But this is not sufficenat at all as the CachingConnectionFactory caches
single connection. Hence i am expecting to have pool of connection so that i
can handle this huge load.
Reg the memory setting, i gone upto -Xmx2048m (on my 64 bit RHEL 5.x) by
which i can add upto 4000 routes to the camle context. I could not go beyond
this limit.
