Re: jkmanager node limitation
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 Err CE RE Wr Rd BusyMax Route RR Cd Rs [E|R] NODE1 ajp13 10.0.0.112:8109 10.0.0.112:8109 STP OK/IDLE 0 1 1 0 0 0 0 0 0 0 0 0 NODE1 WwwNODE1Com 0/0 Then I would call the following url to Activate the node. http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waNODE1=activate Go to the esit page and do the same change via the GUI. After committing the change in the GUI, there should be the correct URL in the browser URL line for a couple of seconds, before the browser gets redirected to the start page. The only parameter, which will be missing, is mime, which is not very important and will only format the OK message slightly different, in case you want to evaluate it later in your script client. You can also have a look at the form contents. See below, for what I expect as a correct URL. This would result in Result: type=OK message=Action finished But the node does not get activated. Please advice. Thanks and regards Mohan Rainer Jung-3 wrote: Mladen Turk wrote: Mohan2005 wrote: Examples: cmd=update mime=txt w=myloadbalancer sw=memberofloadbalancer wa=disabled http://localhost/jkmanager/?cmd=updatemime=txtw=TESTsw=NODE1wa=activate Mass editing of one attribute for all sub workers (also called edit by aspect) could be done via cmd=update mime=txt w=myloadbalancer att=wa val1=disabled val2=active val3=disabled val4=disabled val5=active http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waval1=activate Regards, Rainer - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jkmanager node limitation
Hello Rainer I am using mod_jk 1.2.25 And I assume val1 is the name of the node (NODE1 in this case) so I tried both http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waNODE1=activate and http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waval1=activate But did not activate a stopped node. (NODE1 in this case) Thanks you for your help and attention to this. Regards Mohan Rainer Jung-3 wrote: 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 Err CE RE Wr Rd BusyMax Route RR Cd Rs [E|R]NODE1 ajp13 10.0.0.112:8109 10.0.0.112:8109 STP OK/IDLE 0 1 1 0 0 00 00 0 0 0 NODE1 WwwNODE1Com 0/0 Then I would call the following url to Activate the node. http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waNODE1=activate Go to the esit page and do the same change via the GUI. After committing the change in the GUI, there should be the correct URL in the browser URL line for a couple of seconds, before the browser gets redirected to the start page. The only parameter, which will be missing, is mime, which is not very important and will only format the OK message slightly different, in case you want to evaluate it later in your script client. You can also have a look at the form contents. See below, for what I expect as a correct URL. This would result in Result: type=OK message=Action finished But the node does not get activated. Please advice. Thanks and regards Mohan Rainer Jung-3 wrote: Mladen Turk wrote: Mohan2005 wrote: Examples: cmd=update mime=txt w=myloadbalancer sw=memberofloadbalancer wa=disabled http://localhost/jkmanager/?cmd=updatemime=txtw=TESTsw=NODE1wa=activate Mass editing of one attribute for all sub workers (also called edit by aspect) could be done via cmd=update mime=txt w=myloadbalancer att=wa val1=disabled val2=active val3=disabled val4=disabled val5=active http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waval1=activate Regards, Rainer - 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-tp17720375p17775050.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 commands, e-mail: [EMAIL PROTECTED]
Re: 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 http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waNODE1=activate This won't work. and http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waval1=activate What's the difference betwen this, and what you get, when you do it via the GUI? It is so much easier to get the right URL by simply doing it once via the GUI. But did not activate a stopped node. (NODE1 in this case) Thanks you for your help and attention to this. Regards Mohan Rainer Rainer Jung-3 wrote: 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 Err CE RE Wr Rd BusyMax Route RR Cd Rs [E|R] NODE1 ajp13 10.0.0.112:8109 10.0.0.112:8109 STP OK/IDLE 0 1 1 0 0 0 0 0 0 0 0 0 NODE1 WwwNODE1Com 0/0 Then I would call the following url to Activate the node. http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waNODE1=activate Go to the esit page and do the same change via the GUI. After committing the change in the GUI, there should be the correct URL in the browser URL line for a couple of seconds, before the browser gets redirected to the start page. The only parameter, which will be missing, is mime, which is not very important and will only format the OK message slightly different, in case you want to evaluate it later in your script client. You can also have a look at the form contents. See below, for what I expect as a correct URL. This would result in Result: type=OK message=Action finished But the node does not get activated. Please advice. Thanks and regards Mohan Rainer Jung-3 wrote: Mladen Turk wrote: Mohan2005 wrote: Examples: cmd=update mime=txt w=myloadbalancer sw=memberofloadbalancer wa=disabled http://localhost/jkmanager/?cmd=updatemime=txtw=TESTsw=NODE1wa=activate Mass editing of one attribute for all sub workers (also called edit by aspect) could be done via cmd=update mime=txt w=myloadbalancer att=wa val1=disabled val2=active val3=disabled val4=disabled val5=active http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waval1=activate Regards, Rainer - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jkmanager node limitation
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 and not at 1. Sorry. Can you confirm, that it works? If so, I'll correct the docs. Rainer - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jkmanager node limitation
Yes :-) That works like a beauty. Thanks a lot again. I will document this. Regards Mohan Mohan2005 wrote: 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-tp17720375p17775798.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 commands, e-mail: [EMAIL PROTECTED]
Re: jkmanager node limitation
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 ? Or is the only way to edit the workers.properties file and use the 'activation' keyword. Example to activate node1000 worker.node1000.activation=s and worker.node1000.activation=Active thanks and regards Mohan Mohan2005 wrote: Thank you. Mladen Turk-4 wrote: 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] -- View this message in context: http://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 commands, e-mail: [EMAIL PROTECTED]
Re: jkmanager node limitation
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 (same rules as for JkMount) I would suggest you fill in the bugzilla enhancement request for Native:JK component at: https://issues.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%206 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]
Re: jkmanager node limitation
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 processing for worker names (same rules as for JkMount) I would suggest you fill in the bugzilla enhancement request for Native:JK component at: https://issues.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%206 Yes, please add an issue about status worker and using patterns for worker and sub worker. In the meantime, you can try to automate the activation setting for multiple workers by using a script. The details for the status worker URL arguments can be found on the page http://tomcat.apache.org/connectors-doc/reference/status.html#Request%20Parameters and you can always check, which URLs get used by interactive usage, because we never use POST. Examples: cmd=update mime=txt w=myloadbalancer sw=memberofloadbalancer wa=disabled Mass editing of one attribute for all sub workers (also called edit by aspect) could be done via cmd=update mime=txt w=myloadbalancer att=wa val1=disabled val2=active val3=disabled val4=disabled val5=active Of course this only works as long as the URL doesn't get to long. There's no guarantee about the order of the sub workers though, so you first need to check the order resulting from your config in the GUI of the status worker. Regards, Rainer - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jkmanager node limitation
Thank you. I will. Regards mohan Rainer Jung-3 wrote: 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 processing for worker names (same rules as for JkMount) I would suggest you fill in the bugzilla enhancement request for Native:JK component at: https://issues.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%206 Yes, please add an issue about status worker and using patterns for worker and sub worker. In the meantime, you can try to automate the activation setting for multiple workers by using a script. The details for the status worker URL arguments can be found on the page http://tomcat.apache.org/connectors-doc/reference/status.html#Request%20Parameters and you can always check, which URLs get used by interactive usage, because we never use POST. Examples: cmd=update mime=txt w=myloadbalancer sw=memberofloadbalancer wa=disabled Mass editing of one attribute for all sub workers (also called edit by aspect) could be done via cmd=update mime=txt w=myloadbalancer att=wa val1=disabled val2=active val3=disabled val4=disabled val5=active Of course this only works as long as the URL doesn't get to long. There's no guarantee about the order of the sub workers though, so you first need to check the order resulting from your config in the GUI of the status worker. Regards, Rainer - 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-tp17720375p17767755.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 commands, e-mail: [EMAIL PROTECTED]
Re: jkmanager node limitation
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 Err CE RE Wr Rd BusyMax Route RR Cd Rs [E|R] NODE1 ajp13 10.0.0.112:8109 10.0.0.112:8109 STP OK/IDLE 0 1 1 0 0 0 0 0 0 0 0 0 NODE1 WwwNODE1Com 0/0 Then I would call the following url to Activate the node. http://localhost/jkmanager/?cmd=updatemime=txtw=TESTatt=waNODE1=activate This would result in Result: type=OK message=Action finished But the node does not get activated. Please advice. Thanks and regards Mohan Rainer Jung-3 wrote: 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 processing for worker names (same rules as for JkMount) I would suggest you fill in the bugzilla enhancement request for Native:JK component at: https://issues.apache.org/bugzilla/enter_bug.cgi?product=Tomcat%206 Yes, please add an issue about status worker and using patterns for worker and sub worker. In the meantime, you can try to automate the activation setting for multiple workers by using a script. The details for the status worker URL arguments can be found on the page http://tomcat.apache.org/connectors-doc/reference/status.html#Request%20Parameters and you can always check, which URLs get used by interactive usage, because we never use POST. Examples: cmd=update mime=txt w=myloadbalancer sw=memberofloadbalancer wa=disabled Mass editing of one attribute for all sub workers (also called edit by aspect) could be done via cmd=update mime=txt w=myloadbalancer att=wa val1=disabled val2=active val3=disabled val4=disabled val5=active Of course this only works as long as the URL doesn't get to long. There's no guarantee about the order of the sub workers though, so you first need to check the order resulting from your config in the GUI of the status worker. Regards, Rainer - 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-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] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jkmanager node limitation
Thank you. Mladen Turk-4 wrote: 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] -- 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. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jkmanager node limitation
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 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 commands, e-mail: [EMAIL PROTECTED]
Re: jkmanager node limitation
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]
