Mohan2005 schrieb:
Hello Again;
I tried the following, did not take effect;
What am I doing wrong here please;
My jkmanager shows this for the Loadbalancer TEST and it has only one node
called NODE1
NameTypeHostAddrAct State D F M
V Acc
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/jkmanager-node-limitation
Mohan2005 schrieb:
Hello Rainer
I am using mod_jk 1.2.25
And I assume val1 is the name of the node (NODE1 in this case)
No, val1 ist the value for the first member of the load balancer, val2
for the second and so on. So it is meant as is.
so I tried both
Again replying to myself:
Rainer Jung schrieb:
Rainer Jung schrieb:
http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waval1=activate
The correct URL is:
http://localhost/jkstatus?cmd=updatemime=txtw=TESTatt=waval0=activ
The only difference is, that the number behind val starts at 0
Mohan
--
View this message in context:
http://www.nabble.com/jkmanager-node-limitation-tp17720375p17775798.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users
://www.nabble.com/jkmanager-node-limitation-tp17720375p17757922.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Mohan2005 wrote:
On the same front, say we have 50 nodes and one jkmanager.
There would be a management problem to disable/activate nodes.
Is there a way to disable/activate nodes passing URL parameters to jkmanager
?
No, but that's a good idea to put a wildchar processing
for worker names
Mladen Turk wrote:
Mohan2005 wrote:
On the same front, say we have 50 nodes and one jkmanager.
There would be a management problem to disable/activate nodes.
Is there a way to disable/activate nodes passing URL parameters to
jkmanager
?
No, but that's a good idea to put a wildchar
]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/jkmanager-node-limitation-tp17720375p17767755.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start
://www.nabble.com/jkmanager-node-limitation-tp17720375p17769461.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/jkmanager-node-limitation-tp17720375p17732214.html
Sent from the Tomcat - User mailing list archive at Nabble.com
Hello All;
Can you please tell me the maximum number of nodes a JkManager can handle
without any issues ?
Assume a Quad-Core large memory system.
Thanks and Regards
Mohan
--
View this message in context:
http://www.nabble.com/jkmanager-node-limitation-tp17720375p17720375.html
Sent from
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
13 matches
Mail list logo
