Re: Tomcat 6.O ajp thread issue
Thanks Mark, I have following configuration, is there anything else do i need configure ..please suggest ..as i am still able to see ajp port in Probe application with default thread count. Executor name=abc namePrefix=catalina-exec- maxThreads=150 minSpareThreads=40 / Connector port=1080 protocol=AJP/1.3 redirectPort=8443 executor=abc/ Thanks, Vicky On Nov 5, 2012, at 1:27 PM, Mark Eggers its_toas...@yahoo.com wrote: On 11/4/2012 11:18 PM, vicky007aggar...@yahoo.co.in wrote: Hi All, I have defined one executor tag in server.xml , which i am referring for both protocols i.e http Ajp. Strange thing is when i am checking the MaxThreadsCount for ajp protocol using Probe application its not showing the value configured in executor instead ajp protocol is still showing the default value of 200 corresponding to MaxThreads attribute. Any thoughts on this behavior ?? Thanks, Vicky If you have the connector configured correctly, the ajp- (where is the port) will not show up in the Thread Pool section of the probe application. You should only see the Executor thread pool. At least this is what I saw on my quick test running Tomcat 6.0.35 on Windows 7 Home Premium 64 bit with JRE 1.7.0_09. . . . (I'll upgrade to 6.0.36 now that my test and production platforms are upgraded.) . . . . just my two cents. /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.O ajp thread issue
On 11/5/2012 12:22 AM, vicky007aggar...@yahoo.co.in wrote: Thanks Mark, I have following configuration, is there anything else do i need configure ..please suggest ..as i am still able to see ajp port in Probe application with default thread count. Executor name=abc namePrefix=catalina-exec- maxThreads=150 minSpareThreads=40 / Connector port=1080 protocol=AJP/1.3 redirectPort=8443 executor=abc/ Thanks, Vicky On Nov 5, 2012, at 1:27 PM, Mark Eggers its_toas...@yahoo.com wrote: On 11/4/2012 11:18 PM, vicky007aggar...@yahoo.co.in wrote: Hi All, I have defined one executor tag in server.xml , which i am referring for both protocols i.e http Ajp. Strange thing is when i am checking the MaxThreadsCount for ajp protocol using Probe application its not showing the value configured in executor instead ajp protocol is still showing the default value of 200 corresponding to MaxThreads attribute. Any thoughts on this behavior ?? Thanks, Vicky If you have the connector configured correctly, the ajp- (where is the port) will not show up in the Thread Pool section of the probe application. You should only see the Executor thread pool. At least this is what I saw on my quick test running Tomcat 6.0.35 on Windows 7 Home Premium 64 bit with JRE 1.7.0_09. . . . (I'll upgrade to 6.0.36 now that my test and production platforms are upgraded.) . . . . just my two cents. /mde/ This is mine, and it worked fine: Executor name=tomcatThreadPool namePrefix=catalina-exec- maxThreads=150 minSpareThreads=4/ Connector port=8009 executor=tomcatThreadPool protocol=AJP/1.3 URIEncoding=UTF-8 redirectPort=8443/ I didn't actually connect to an Apache server, but I would still see a thread pool if one existed. I do when I use the Connector-based configuration, and only see the Executor thread pool when using the Executor configuration. Make sure you're using the server.xml that you think you are. Last time I think you were still using the Connector-based server.xml. . . . . just my two cents /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.O ajp thread issue
Thanks Mark for ur comments .but i didnt understand what you mean by following line ;- I think you were still using the Connector-based server.xml. I am using below executor for both ajp http but why i am still seeing the ajp default thread count in probe application. I didnt find it . I am not using apache for this. But i want to validate that executor can override the default thread count setting of ajp connector when defined. Pls suggest Executor name=abc namePrefix=catalina-exec- maxThreads=150 minSpareThreads=40 / Thanks, Vicky On Nov 5, 2012, at 2:01 PM, Mark Eggers its_toas...@yahoo.com wrote: I think you were still using the Connector-based server.xml. Thanks, Vicky Sent from my iPhone On Nov 5, 2012, at 2:01 PM, Mark Eggers its_toas...@yahoo.com wrote: On 11/5/2012 12:22 AM, vicky007aggar...@yahoo.co.in wrote: Thanks Mark, I have following configuration, is there anything else do i need configure ..please suggest ..as i am still able to see ajp port in Probe application with default thread count. Executor name=abc namePrefix=catalina-exec- maxThreads=150 minSpareThreads=40 / Connector port=1080 protocol=AJP/1.3 redirectPort=8443 executor=abc/ Thanks, Vicky On Nov 5, 2012, at 1:27 PM, Mark Eggers its_toas...@yahoo.com wrote: On 11/4/2012 11:18 PM, vicky007aggar...@yahoo.co.in wrote: Hi All, I have defined one executor tag in server.xml , which i am referring for both protocols i.e http Ajp. Strange thing is when i am checking the MaxThreadsCount for ajp protocol using Probe application its not showing the value configured in executor instead ajp protocol is still showing the default value of 200 corresponding to MaxThreads attribute. Any thoughts on this behavior ?? Thanks, Vicky If you have the connector configured correctly, the ajp- (where is the port) will not show up in the Thread Pool section of the probe application. You should only see the Executor thread pool. At least this is what I saw on my quick test running Tomcat 6.0.35 on Windows 7 Home Premium 64 bit with JRE 1.7.0_09. . . . (I'll upgrade to 6.0.36 now that my test and production platforms are upgraded.) . . . . just my two cents. /mde/ This is mine, and it worked fine: Executor name=tomcatThreadPool namePrefix=catalina-exec- maxThreads=150 minSpareThreads=4/ Connector port=8009 executor=tomcatThreadPool protocol=AJP/1.3 URIEncoding=UTF-8 redirectPort=8443/ I didn't actually connect to an Apache server, but I would still see a thread pool if one existed. I do when I use the Connector-based configuration, and only see the Executor thread pool when using the Executor configuration. Make sure you're using the server.xml that you think you are. Last time I think you were still using the Connector-based server.xml. . . . . just my two cents /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.O ajp thread issue
Vicky, you keep on top-posting, which is annoying and makes it difficult to follow the conversation. Please answer below the questions and suggestions of other people. My question is : apart from what the various probe programs show you as counters, are you actually *seeing* a number of Tomcat threads being created, that is different from your expectations ? What I am trying to say is : the various probe and watchdog programs show the content of some attribute or variable which they request through JMX or whatever, by name. But this particular setting that they are showing, may be ignored by Tomcat under some circumstances, and Tomcat may be using a different setting than the one which the probe is requesting. In other words, maybe the probe program that you are using is just not smart enough to know that when there is an Executor, then the value stored in the Connector is meaningless, and they should ask for another name/value. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.O ajp thread issue
Andre- i am facing issue thats y i m Posting. I didnt intend to spam please. In probe , http values are displayed correctly but not the ajp one. Thanks, Vicky On Nov 5, 2012, at 4:35 PM, André Warnier a...@ice-sa.com wrote: Vicky, you keep on top-posting, which is annoying and makes it difficult to follow the conversation. Please answer below the questions and suggestions of other people. My question is : apart from what the various probe programs show you as counters, are you actually *seeing* a number of Tomcat threads being created, that is different from your expectations ? What I am trying to say is : the various probe and watchdog programs show the content of some attribute or variable which they request through JMX or whatever, by name. But this particular setting that they are showing, may be ignored by Tomcat under some circumstances, and Tomcat may be using a different setting than the one which the probe is requesting. In other words, maybe the probe program that you are using is just not smart enough to know that when there is an Executor, then the value stored in the Connector is meaningless, and they should ask for another name/value. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.O ajp thread issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vicky, On 11/5/12 2:18 AM, vicky007aggar...@yahoo.co.in wrote: I have defined one executor tag in server.xml , which i am referring for both protocols i.e http Ajp. You should post your configuration. I see you posted a followup which included your Connector and Executor configuration but nobody should have asked to see it. Remember that list members are volunteers and their primary job function isn't to track your progress with your environment. If you start a new thread, re-post all your current configuration so the community doesn't have to go hunting through your old posts to see what is really going on. Strange thing is when i am checking the MaxThreadsCount for ajp protocol using Probe application its not showing the value configured in executor instead ajp protocol is still showing the default value of 200 corresponding to MaxThreads attribute. Which Probe application? Which JMX bean? Which property? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCYiIIACgkQ9CaO5/Lv0PCulACgm5vZhs4RMGZc1bckimRPqHU7 lTUAn0fLi2a4f/cCRZnFg8RDOJe+a+j3 =cj3q -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 6.O ajp thread issue
Hi All, I have defined one executor tag in server.xml , which i am referring for both protocols i.e http Ajp. Strange thing is when i am checking the MaxThreadsCount for ajp protocol using Probe application its not showing the value configured in executor instead ajp protocol is still showing the default value of 200 corresponding to MaxThreads attribute. Any thoughts on this behavior ?? Thanks, Vicky - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.O ajp thread issue
On 11/4/2012 11:18 PM, vicky007aggar...@yahoo.co.in wrote: Hi All, I have defined one executor tag in server.xml , which i am referring for both protocols i.e http Ajp. Strange thing is when i am checking the MaxThreadsCount for ajp protocol using Probe application its not showing the value configured in executor instead ajp protocol is still showing the default value of 200 corresponding to MaxThreads attribute. Any thoughts on this behavior ?? Thanks, Vicky If you have the connector configured correctly, the ajp- (where is the port) will not show up in the Thread Pool section of the probe application. You should only see the Executor thread pool. At least this is what I saw on my quick test running Tomcat 6.0.35 on Windows 7 Home Premium 64 bit with JRE 1.7.0_09. . . . (I'll upgrade to 6.0.36 now that my test and production platforms are upgraded.) . . . . just my two cents. /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
