Re: Q: Current Stable Tomcat/Java Versions/Settings
Thanks.. We're not on 7.6 yet because the 7.6 midtier apparently doesn't support 7.0.1 database servers. We're trying to get the database servers all upgraded to 7.5 as well before moving to v7.6. Until then, we need a stable midtier. The bundled Tomcat version in 7.5 P6 appears to be v5.5.28. Are those settings you mentioned below applicable to 5x Tomcat? Willing to remove the threads setting if not recommended. If anyone knows why that's a bad thing--please respond. Craig Carter Information Technology Manager, RSP -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of strauss Sent: Tuesday, November 30, 2010 9:01 AM To: arslist@ARSLIST.ORG Subject: Re: Q: Current Stable Tomcat/Java Versions/Settings ** "Service not available" is an error that I had never seen until 7.6.03, when I was forced to use the Jakarta plugin with IIS because the 6.0.18 tomcat bundled with mid-tier 7.6.03 refuses to work with OpenSSL. Prior to this I have always installed the mid-tier using tomcat as the web server, not IIS. BTW, at some point during production with 7.1 BMC Support admitted to me that the 3000 threads settings they had documented in the past was an error, and should not be set at all. Eventually it dropped out of the mid-tier docs. Recently they told me that under Java Options: in the Apache Tomcat Tomcat6 Properties box, I should add the line: -XX:MaxPermSize=256m Apparently the mid-tier installer already adds the settings: -Xincgc -XX:PermSize=256m Adding this setting has cleared up some out of memory errors that I have seen when trying to load the RKM 7.6.03 console in mid-tier, among other things. These do not appear to be standard settings in a tomcat install - yesterday I built a midtier 7.6.03 on the 64-bit Windows distribution of tomcat 6.0.28 (trying to find a tomcat 6.0 build that will not only do SSL using a commercial certificate, but will work properly with mid-tier 7.6.03; the most current tomcat - 6.0.29 - had problems with mid-tier), and I had to add all three of the -X lines to the Java Options. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ <http://itsm.unt.edu/> From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Craig Carter Sent: Tuesday, November 30, 2010 8:15 AM To: arslist@ARSLIST.ORG Subject: Q: Current Stable Tomcat/Java Versions/Settings ** All, We recently upgraded all of our midtier servers and we're having repeated problems with Tomcat "locking up" and displaying "Service not available". It appears to happen randomly and at no set memory limit. The last couple of times was in the 600-700MB in use when it happened. The service fails to stop or restart and has to be killed to get it started again. We're running the following: ARS 7.5 P6 Apache Tomcat 5.5.28 Java 1.6.0_21 Windows Server 2008/IIS7 Tomcat settings are 512MB initial, 1536MB maximum, and 3000 threads. We've always used ServletExec in the past. Those of you with a lot of Tomcat experience, what combination of versions/memory sizes have you found to be the most stable for ARS 7.5? Thanks, Craig Carter Information Technology Manager, RSP _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Q: Current Stable Tomcat/Java Versions/Settings
"Service not available"; I believe this happens when mod_jk can't connect to Tomcat. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: Q: Current Stable Tomcat/Java Versions/Settings
"Service not available" is an error that I had never seen until 7.6.03, when I was forced to use the Jakarta plugin with IIS because the 6.0.18 tomcat bundled with mid-tier 7.6.03 refuses to work with OpenSSL. Prior to this I have always installed the mid-tier using tomcat as the web server, not IIS. BTW, at some point during production with 7.1 BMC Support admitted to me that the 3000 threads settings they had documented in the past was an error, and should not be set at all. Eventually it dropped out of the mid-tier docs. Recently they told me that under Java Options: in the Apache Tomcat Tomcat6 Properties box, I should add the line: -XX:MaxPermSize=256m Apparently the mid-tier installer already adds the settings: -Xincgc -XX:PermSize=256m Adding this setting has cleared up some out of memory errors that I have seen when trying to load the RKM 7.6.03 console in mid-tier, among other things. These do not appear to be standard settings in a tomcat install - yesterday I built a midtier 7.6.03 on the 64-bit Windows distribution of tomcat 6.0.28 (trying to find a tomcat 6.0 build that will not only do SSL using a commercial certificate, but will work properly with mid-tier 7.6.03; the most current tomcat - 6.0.29 - had problems with mid-tier), and I had to add all three of the -X lines to the Java Options. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Craig Carter Sent: Tuesday, November 30, 2010 8:15 AM To: arslist@ARSLIST.ORG Subject: Q: Current Stable Tomcat/Java Versions/Settings ** All, We recently upgraded all of our midtier servers and we're having repeated problems with Tomcat "locking up" and displaying "Service not available". It appears to happen randomly and at no set memory limit. The last couple of times was in the 600-700MB in use when it happened. The service fails to stop or restart and has to be killed to get it started again. We're running the following: ARS 7.5 P6 Apache Tomcat 5.5.28 Java 1.6.0_21 Windows Server 2008/IIS7 Tomcat settings are 512MB initial, 1536MB maximum, and 3000 threads. We've always used ServletExec in the past. Those of you with a lot of Tomcat experience, what combination of versions/memory sizes have you found to be the most stable for ARS 7.5? Thanks, Craig Carter Information Technology Manager, RSP _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Q: Current Stable Tomcat/Java Versions/Settings
Hello, I wrote a post on this topic earlier this year: http://www.javasystemsolutions.com/arslist/view/89025846 In a nutshell, start by setting the initial heap size to 90% of the maximum, so -Xms1400 -Xmx1536 in yuor case. Your current setup is encouraging the garbage collector to invoke a huge clean up of 1Gb, which will exhibit itself in the VM appearing to lock up. If you're using Apache and mod_jk, be sure to run mod_jk 1.2.31. There's a critical bug (https://issues.apache.org/bugzilla/show_bug.cgi?id=48169) in mod_jk which causes delays when dealing with AJP sockets that are not properly closed - we helped them resolve it so I can confirm it did exist. This may not be the problem, but it's worth considering. Finally, review your Midtier caching to see why it's consuming all this memory. I can't imagine ServletExec being much better than Tomcat - did you upgrade when you moved to Tomcat? John -- Single Sign On for AR System http://www.javasystemsolutions.com/jss/ssoplugin ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Q: Current Stable Tomcat/Java Versions/Settings
All, We recently upgraded all of our midtier servers and we're having repeated problems with Tomcat "locking up" and displaying "Service not available". It appears to happen randomly and at no set memory limit. The last couple of times was in the 600-700MB in use when it happened. The service fails to stop or restart and has to be killed to get it started again. We're running the following: ARS 7.5 P6 Apache Tomcat 5.5.28 Java 1.6.0_21 Windows Server 2008/IIS7 Tomcat settings are 512MB initial, 1536MB maximum, and 3000 threads. We've always used ServletExec in the past. Those of you with a lot of Tomcat experience, what combination of versions/memory sizes have you found to be the most stable for ARS 7.5? Thanks, Craig Carter Information Technology Manager, RSP ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
