Re: maxProcessors vs maxThreads
Cox, Charlie [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Is there a similar setting for jk2 under 4.1.29? The connector code is the same, so the same setting should work. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Tuesday, January 20, 2004 2:16 AM To: [EMAIL PROTECTED] Subject: Re: maxProcessors vs maxThreads Oh, come on, get real :). The Jk-Coyote docs are probably second to the mod_jk2 docs for being the most incomplete. While (as Remy has stated), you can perfectly happily set this on the Connector, the jk2.properties syntax is: container.maxThreads=value Shapira, Yoav [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Howdy, thanks yoav, i noticed that but then does that mean that there is no method to specify max threads/processors for the coyote ajp connector? that sounds a bit strange If it's not documented, then there's no configurable way to do it. Of course, you can always subclass/extend a connector just like any other tomcat element to add the behavior you want. how does tomcat behave with the ajp connector? does it indefinitely spawn threads to handle requests until it bombs out of memory? or is there behaviour as specified by the acceptcount/max processors for the http connector buried in the code of the ajp connector that can't be modified? I don't use the AJP connector, so I can't answer that one, but the code is open for you to inspect at your leisure... Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maxProcessors vs maxThreads
I'd go with 'or'. In the TC 3.x line, the HTTP Connector really s*cked (except that with the TC 3.3.2-dev nightly, you have the option of using the same CoyoteConnector as TC 4.1.x-5.0.x :). Unless you *need* the features of e.g. mod_rewrite, mod_php, I'd agree with Yoav, and you should use Tomcat as stand-alone. Shapira, Yoav [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Howdy, Hm, we have setup IIS in front of Tomcat so it can serve off the static content, I thought that was the conventional wisdom. Conventional and/or outdated. Or is the more likely operator in the previous sentence. We're looking at about 300+ users of which maybe lets say 20 concurrent at quiet times, probably approaching 100+ when we announce something. Would you say Tomcat can handle that fairly well including the static stuff? Yeah, I would, but the specifics depend on your application, your hardware, your OS. It's not hard to test: put together a JMeter (or AB, or Grinder, or whatever tool you like) test plan that simulates however many concurrent users you expect, run it on tomcat standalone, on tomcat with IIS, on a cluster, iteratively tune the system, and see what happens. Would I just need to look at server.xml to get more performance from Tomcat (exluding the JProfiler run) or is a cluster a really good idea too. If a Again, depends on your requirements. Clusters increase setup and maintenance costs, but can also increase reliability and possibly performance if you balance the load in the cluster. Read Filip Hanik's various docs and articles on tomcat clustering. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maxProcessors vs maxThreads
Oh, come on, get real :). The Jk-Coyote docs are probably second to the mod_jk2 docs for being the most incomplete. While (as Remy has stated), you can perfectly happily set this on the Connector, the jk2.properties syntax is: container.maxThreads=value Shapira, Yoav [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Howdy, thanks yoav, i noticed that but then does that mean that there is no method to specify max threads/processors for the coyote ajp connector? that sounds a bit strange If it's not documented, then there's no configurable way to do it. Of course, you can always subclass/extend a connector just like any other tomcat element to add the behavior you want. how does tomcat behave with the ajp connector? does it indefinitely spawn threads to handle requests until it bombs out of memory? or is there behaviour as specified by the acceptcount/max processors for the http connector buried in the code of the ajp connector that can't be modified? I don't use the AJP connector, so I can't answer that one, but the code is open for you to inspect at your leisure... Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Howdy, Oh, come on, get real :). The Jk-Coyote docs are probably second to the mod_jk2 docs for being the most incomplete. We should probably do something about that, then ;) I've paid much more attention to the tomcat (core) docs rather than the connector-related stuff, naturally, as I don't use the connectors ;) If people have doc patches/suggestions for the connectors as well as anything else in tomcat, I'm always happy to review/commit/maybe address them. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Hi Yoav, You seem to know what you are talking about and it amuses me everyday you come on at the same sort of time and bang off all the answers :) (although regrettably I was hoping you would answer my Tomcat and Clusters one yesterday). Anyways, if someone like you is not using the connectors, is that because there is something better to use? ADC -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 20 January 2004 13:57 To: Tomcat Users List Subject: RE: maxProcessors vs maxThreads Howdy, Oh, come on, get real :). The Jk-Coyote docs are probably second to the mod_jk2 docs for being the most incomplete. We should probably do something about that, then ;) I've paid much more attention to the tomcat (core) docs rather than the connector-related stuff, naturally, as I don't use the connectors ;) If people have doc patches/suggestions for the connectors as well as anything else in tomcat, I'm always happy to review/commit/maybe address them. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Is there a similar setting for jk2 under 4.1.29? -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Tuesday, January 20, 2004 2:16 AM To: [EMAIL PROTECTED] Subject: Re: maxProcessors vs maxThreads Oh, come on, get real :). The Jk-Coyote docs are probably second to the mod_jk2 docs for being the most incomplete. While (as Remy has stated), you can perfectly happily set this on the Connector, the jk2.properties syntax is: container.maxThreads=value Shapira, Yoav [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Howdy, thanks yoav, i noticed that but then does that mean that there is no method to specify max threads/processors for the coyote ajp connector? that sounds a bit strange If it's not documented, then there's no configurable way to do it. Of course, you can always subclass/extend a connector just like any other tomcat element to add the behavior you want. how does tomcat behave with the ajp connector? does it indefinitely spawn threads to handle requests until it bombs out of memory? or is there behaviour as specified by the acceptcount/max processors for the http connector buried in the code of the ajp connector that can't be modified? I don't use the AJP connector, so I can't answer that one, but the code is open for you to inspect at your leisure... Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Howdy, You seem to know what you are talking about and it amuses me everyday you come on at the same sort of time and bang off all the answers :) (although regrettably I was hoping you would answer my Tomcat and Clusters one yesterday). I work normal hours, roughly 8:30-4:30 at my day job, US Eastern time zone (I live in Boston), so yeah it's about the same time every day ;) Anyways, if someone like you is not using the connectors, is that because there is something better to use? Tomcat standalone. I have yet to find a single production system that required apache in front of tomcat, and I've put more systems than I care to count in production for various clients in various industries and technical environments. And every time, the simplicity, ease of deployment, and ease of maintenance added significant value that can be measured in $$$. Most of these apps had strict contractually-defined performance goals, and in those cases we tested rigorously to make sure tomcat by itself performs well enough to handle the expected maximum loads. And that's why I don't bother to keep up with the connectors, their configuration, deployment, architecture, supported features, etc. If I ever find a system that requires them, I might give it a shot then. But this is why I laugh when people start off when a setup involving apache and connectors without making sure they really need them ;) Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
It depends on your needs and requirements. If you don't need apache in front of tomcat, then you just need a http connector. -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 3:00 PM To: Tomcat Users List Subject: RE: maxProcessors vs maxThreads Hi Yoav, Anyways, if someone like you is not using the connectors, is that because there is something better to use? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Hm, we have setup IIS in front of Tomcat so it can serve off the static content, I thought that was the conventional wisdom. We're looking at about 300+ users of which maybe lets say 20 concurrent at quiet times, probably approaching 100+ when we announce something. Would you say Tomcat can handle that fairly well including the static stuff? Would I just need to look at server.xml to get more performance from Tomcat (exluding the JProfiler run) or is a cluster a really good idea too. If a cluster is a good idea I'd be eternally grateful for some pointers on good docs to set a TC5 cluster up and a free stable load balancer to work with that. I think Professonal Tomcat 5 comes out in May but that's too late for me ;) Regards, ADC. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 20 January 2004 15:58 To: Tomcat Users List Subject: RE: maxProcessors vs maxThreads Howdy, You seem to know what you are talking about and it amuses me everyday you come on at the same sort of time and bang off all the answers :) (although regrettably I was hoping you would answer my Tomcat and Clusters one yesterday). I work normal hours, roughly 8:30-4:30 at my day job, US Eastern time zone (I live in Boston), so yeah it's about the same time every day ;) Anyways, if someone like you is not using the connectors, is that because there is something better to use? Tomcat standalone. I have yet to find a single production system that required apache in front of tomcat, and I've put more systems than I care to count in production for various clients in various industries and technical environments. And every time, the simplicity, ease of deployment, and ease of maintenance added significant value that can be measured in $$$. Most of these apps had strict contractually-defined performance goals, and in those cases we tested rigorously to make sure tomcat by itself performs well enough to handle the expected maximum loads. And that's why I don't bother to keep up with the connectors, their configuration, deployment, architecture, supported features, etc. If I ever find a system that requires them, I might give it a shot then. But this is why I laugh when people start off when a setup involving apache and connectors without making sure they really need them ;) Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Howdy, Hm, we have setup IIS in front of Tomcat so it can serve off the static content, I thought that was the conventional wisdom. Conventional and/or outdated. Or is the more likely operator in the previous sentence. We're looking at about 300+ users of which maybe lets say 20 concurrent at quiet times, probably approaching 100+ when we announce something. Would you say Tomcat can handle that fairly well including the static stuff? Yeah, I would, but the specifics depend on your application, your hardware, your OS. It's not hard to test: put together a JMeter (or AB, or Grinder, or whatever tool you like) test plan that simulates however many concurrent users you expect, run it on tomcat standalone, on tomcat with IIS, on a cluster, iteratively tune the system, and see what happens. Would I just need to look at server.xml to get more performance from Tomcat (exluding the JProfiler run) or is a cluster a really good idea too. If a Again, depends on your requirements. Clusters increase setup and maintenance costs, but can also increase reliability and possibly performance if you balance the load in the cluster. Read Filip Hanik's various docs and articles on tomcat clustering. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Thanks Yoav. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 20 January 2004 16:12 To: Tomcat Users List Subject: RE: maxProcessors vs maxThreads Howdy, Hm, we have setup IIS in front of Tomcat so it can serve off the static content, I thought that was the conventional wisdom. Conventional and/or outdated. Or is the more likely operator in the previous sentence. We're looking at about 300+ users of which maybe lets say 20 concurrent at quiet times, probably approaching 100+ when we announce something. Would you say Tomcat can handle that fairly well including the static stuff? Yeah, I would, but the specifics depend on your application, your hardware, your OS. It's not hard to test: put together a JMeter (or AB, or Grinder, or whatever tool you like) test plan that simulates however many concurrent users you expect, run it on tomcat standalone, on tomcat with IIS, on a cluster, iteratively tune the system, and see what happens. Would I just need to look at server.xml to get more performance from Tomcat (exluding the JProfiler run) or is a cluster a really good idea too. If a Again, depends on your requirements. Clusters increase setup and maintenance costs, but can also increase reliability and possibly performance if you balance the load in the cluster. Read Filip Hanik's various docs and articles on tomcat clustering. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maxProcessors vs maxThreads
there seems to be some confusion about whether to use maxThreads or maxProcessors and the effect on tomcat. futher it is not clear from the docs which one to use and whether they have an effect on the protocol used by the connector. could someone please clarify this... using tomcat 5.0.16: the JK2 AJP connector (http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/ajp.html) docs doesn't list any directive like maxProcessors or maxThreads. the HTTP connector does (http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/http.html) list a maxThreads directive. 1. is maxProcessors deprecated? 2. does maxProcessors and/or maxThreads apply to the AJP connector? 3. if i do set maxProcessors/maxThreads does the total number of maxThreads/maxProcessors across all tomcat instances in a load balanced setup need to equal/less than/greater than the apache serverlimit? example: - 2 apache servers with serverlimit 1024 each = total server limit = 2048 - 4 tomcat instances. - should maxProcessors be set to 2048/4 = 512 or less than/greater than that? 4. similiar questions as 12 for maxSpareThreads/maxIdleProcessors and minSpareThreads/minIdleProcessors. 5. does acceptCount work for both HTTP and AJP connectors? thanks in advance for clarifications. here is the ajp connector element in my server.xml !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector address=192.168.100.152 port=8009 redirectPort=8443 debug=0 enableLookups=false protocol=AJP/1.3 / do i set maxThreads, maxSpareThreads, minSpareThreads, acceptCount or maxProcessors, maxIdleProcessors, minIdleProcessors, acceptCount? apu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Howdy, there seems to be some confusion about whether to use maxThreads or maxProcessors and the effect on tomcat. futher it is not clear from the docs which one to use and whether they have an effect on the protocol used by the connector. Read the documentation carefully. The Coyote (HTTP) connector for Tomcat 5 supports parameters for max threads, spare threads, and other settings. The Coyote (HTTP) connector for tomcat 4 supports maxProcessors, minProcessors, and other settings. Anything not listed on these pages is not supported, meaning Coyote in Tomcat 5 does NOT support maxProcessors and Coyote in tomcat 4 does NOT support max threads. The AJP connector in tomcat 5, as its documentation states, does not support either max threads or maxProcessors. The docs lay it all out. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
thanks yoav, i noticed that but then does that mean that there is no method to specify max threads/processors for the coyote ajp connector? that sounds a bit strange how does tomcat behave with the ajp connector? does it indefinitely spawn threads to handle requests until it bombs out of memory? or is there behaviour as specified by the acceptcount/max processors for the http connector buried in the code of the ajp connector that can't be modified? thanks in advance. Howdy, there seems to be some confusion about whether to use maxThreads or maxProcessors and the effect on tomcat. futher it is not clear from the docs which one to use and whether they have an effect on the protocol used by the connector. Read the documentation carefully. The Coyote (HTTP) connector for Tomcat 5 supports parameters for max threads, spare threads, and other settings. The Coyote (HTTP) connector for tomcat 4 supports maxProcessors, minProcessors, and other settings. Anything not listed on these pages is not supported, meaning Coyote in Tomcat 5 does NOT support maxProcessors and Coyote in tomcat 4 does NOT support max threads. The AJP connector in tomcat 5, as its documentation states, does not support either max threads or maxProcessors. The docs lay it all out. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maxProcessors vs maxThreads
Shapira, Yoav wrote: Howdy, there seems to be some confusion about whether to use maxThreads or maxProcessors and the effect on tomcat. futher it is not clear from the docs which one to use and whether they have an effect on the protocol used by the connector. Read the documentation carefully. The Coyote (HTTP) connector for Tomcat 5 supports parameters for max threads, spare threads, and other settings. The Coyote (HTTP) connector for tomcat 4 supports maxProcessors, minProcessors, and other settings. Anything not listed on these pages is not supported, meaning Coyote in Tomcat 5 does NOT support maxProcessors and Coyote in tomcat 4 does NOT support max threads. The AJP connector in tomcat 5, as its documentation states, does not support either max threads or maxProcessors. The docs lay it all out. For AJP, you're supposed to use the jk2.properties file. This is all in the JK docs, with the native connector docs. Some select parameters from jk2.properties could be set on the Connector element, but it seemed better to use only one configuration file for AJP, and I removed them from the documentation. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Howdy, thanks yoav, i noticed that but then does that mean that there is no method to specify max threads/processors for the coyote ajp connector? that sounds a bit strange If it's not documented, then there's no configurable way to do it. Of course, you can always subclass/extend a connector just like any other tomcat element to add the behavior you want. how does tomcat behave with the ajp connector? does it indefinitely spawn threads to handle requests until it bombs out of memory? or is there behaviour as specified by the acceptcount/max processors for the http connector buried in the code of the ajp connector that can't be modified? I don't use the AJP connector, so I can't answer that one, but the code is open for you to inspect at your leisure... Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
thanks yoav. this begs another question... under what circumstances would one choose to use the ajp connector? i am assuming it's probably a more compact and efficient protocol compared to http (not sure about that). in any case, if one never needs to access tomcat directly from a browser (tomcat is always hidden behind apache on an internal network not accessible from the outside) what parameters should i use to judge whether to use http or ajp connectors? it seems like http is better (due to the fact that you can customize settings like maxThreads) but i was always under the impression that ajp should be preferred over http (i guess i was wrong) any thoughts on this? Howdy, thanks yoav, i noticed that but then does that mean that there is no method to specify max threads/processors for the coyote ajp connector? that sounds a bit strange If it's not documented, then there's no configurable way to do it. Of course, you can always subclass/extend a connector just like any other tomcat element to add the behavior you want. how does tomcat behave with the ajp connector? does it indefinitely spawn threads to handle requests until it bombs out of memory? or is there behaviour as specified by the acceptcount/max processors for the http connector buried in the code of the ajp connector that can't be modified? I don't use the AJP connector, so I can't answer that one, but the code is open for you to inspect at your leisure... Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
On Mon, January 19, 2004 at 1:47 pm, Apu Shah wrote: this begs another question... under what circumstances would one choose to use the ajp connector? i am assuming it's probably a more compact and efficient protocol compared to http (not sure about that). The AJP protocol is designed to be used for webservers to communicate to Tomcat. For example, the mod_jk module for Apache is used to communicate with Tomcat, it proxies requests from Apache to Tomcat. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maxProcessors vs maxThreads
Apu Shah wrote: thanks yoav. this begs another question... under what circumstances would one choose to use the ajp connector? i am assuming it's probably a more compact and efficient protocol compared to http (not sure about that). in any case, if one never needs to access tomcat directly from a browser (tomcat is always hidden behind apache on an internal network not accessible from the outside) what parameters should i use to judge whether to use http or ajp connectors? it seems like http is better (due to the fact that you can customize settings like maxThreads) but i was always under the impression that ajp should be preferred over http (i guess i was wrong) any thoughts on this? AJP and HTTP serve different purposes. AJP is used for Apache to talk to Tomcat. They could use HTTP, I suppose, but AJP is a more efficient protocol. You cannot use directly from your browser to Tomcat using AJP - browsers don't support that protocol. Apache has a module (the mod_jk.dll or the equivalent on Unix) that enables it to communicate using that protocol. You can indeed communicate with Tomcat directly from your browser. If you have it enabled, you can use port 8080 (default value, you can change), so a URL might look like http://yourserver:8080/yourpage.jsp. If you want, you can even cut Apache out completely, and tell Tomcat to handle port 80. Not advisable, though, as Apache has had thousands of hours invested to make it efficient at delivering static content. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maxProcessors vs maxThreads
thanks much remy. i was looking for configuring maxThreads for the ajp connector with jk2. anyways, do you know what the default value for maxThreads is for channelSocket? (it's not in the docs) what are the defaults for the other options? or where can i find them? backLog tcpNoDelay soTimeout soLinger serverTimeout again, thanks. this was exactly what i was looking for. ps: you know if you specify maxProcessors or maxThreads in the ajp Connector element, tomcat starts up fine, without any warnings. as a suggestion, (i don't know how beneficial), but it would probably be nice if a message gets printed in the log (with debug=0) stating that the values will be ignored and should be set in jk2.properties. For AJP, you're supposed to use the jk2.properties file. This is all in the JK docs, with the native connector docs. Some select parameters from jk2.properties could be set on the Connector element, but it seemed better to use only one configuration file for AJP, and I removed them from the documentation. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maxProcessors vs maxThreads
using tomcat 5.0.16 the JK2 AJP connector (http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/ajp.html) docs doesn't list any directive like maxProcessors or maxThreads. the HTTP connector does (http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/http.html) list a maxThreads directive. 1. is maxProcessors deprecated? 2. does maxProcessors and/or maxThreads apply to the AJP connector? 3. if i do set maxProcessors/maxThreads does the total number of maxThreads/maxProcessors across all tomcat instances in a load balanced setup need to equal/less than/greater than the apache serverlimit? example: - 2 apache servers with serverlimit 1024 each = total server limit = 2048 - 4 tomcat instances. - should maxProcessors be set to 2048/4 = 512 or less than/greater than that? 4. similiar questions as 12 for maxSpareThreads/maxIdleProcessors and minSpareThreads/minIdleProcessors. 5. does acceptCount work for both HTTP and AJP connectors? thanks in advance for clarifications. here is the ajp connector element in my server.xml !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector address=192.168.100.152 port=8009 redirectPort=8443 debug=0 enableLookups=false protocol=AJP/1.3 / do i set maxThreads, maxSpareThreads, minSpareThreads, acceptCount or maxProcessors, maxIdleProcessors, minIdleProcessors, acceptCount? apu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
