The problem I have is that I need Tomcat 6 for static cluster membership discovery for Tomcat session replication because our clustering plan cannot be supported by our network infrastructure. With CAS 3.1 requiring Java 1.5 or higher and the fact that Sun Java and Tomcat binaries are fairly easy to install/upgrade/remove, I don't see it as a major hassle to me to manage them manually.
I haven't had any issues with compiling and using the jsvc daemon; just curious as what others are doing. Thanks for the help Josh! Andrew R Feller, Analyst Subversion Administrator University Information Systems Louisiana State University [EMAIL PROTECTED] (office) 225.578.3737 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Josh Kelley Sent: Friday, August 10, 2007 10:14 PM To: Yale CAS mailing list Subject: Re: Tomcat startup/shutdown scripts for RHEL On 8/10/07, Andrew R Feller <[EMAIL PROTECTED]> wrote: > Thanks for the reply Josh! I was wondering if anyone else in the CAS > community even bothered with RHEL for a moment there. > > A couple extra questions for you: > > After looking over the startup and shutdown scripts from the Tomcat > binary distribution, I don't understand where you can specify the user > Tomcat is suppose to run as. I reread your emails and realized that my answer was probably pretty unclear. We're currently using Tomcat 5.5.23 as packaged as an RPM with RHEL (technically, in our case, CentOS) 5. The RPM includes startup and shutdown scripts that take care of running it as the tomcat user (or whatever account you want). I enabled this startup script so that RHEL / CentOS starts Tomcat, instead of my doing it manually. I'm not using jsvc because the scripts provided with the RPM don't use it and so I hadn't even looked at other methods of starting Tomcat. I just now read on the CAS wiki (http://www.ja-sig.org/wiki/display/CASUM/Deploying+CAS+3.0.x+in+RHEL+5+ with+Sun+Java, http://www.ja-sig.org/wiki/display/CASUM/Switching+to+a+Sun+JVM+in+RHEL) that using RHEL's tomcat RPMs isn't really recommended. I personally haven't had any problems doing so. Using it with Sun's Java is painless; I installed Sun's Java as an RPM (using JPackage's java-1.5.0-sun nosrc RPM, NOT Sun's Java RPM + JPackage's java-1.5.0-sun-compat), and RHEL's tomcat immediately picked it up and started using it as its runtime environment. I strongly prefer using the distro's packages rather than manually installing software myself, since I think it gives better integration and easier management and upgrades. If there are any concerns or incompatibilities with RHEL's tomcat, you can always enable JPackage (http://jpackage.org) as a repository and get a non-gcj version of Tomcat from there. I'm a complete novice with regards to Tomcat and am learning it as I go, so take my advice with a grain of salt. However, so far, everything appears to be working with this approach. Anyway, I hope this answers your questions. If there's anything else I can do to help, please let me know. Josh Kelley _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
