Mohan2005 wrote:
Hello All;
Can you please tell me the maximum number of nodes a JkManager can handle
without any issues ?
Theoretically unlimited, but number of workers is defined by int,
thus 2^31 - 1, for 32-bit integer systems.
Each node consumes around 1K of data so multiply that by the number
of nodes and number of child processes, and you'll get a rough estimate
about configuration footprint.
JkManager uses table scan for finding nodes (workers), so it's O(n).
However this is still much faster then any database like structure,
because this data is in shared memory.
In general, the size what jkmanager can handle will be the last
thing you'll need to worry about.
Regards
--
^(TM)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
