There were two problems with tomcat on SLES10 when it first was released. One was a message that showed in the logs about jmx.jar and licensing issues. After installing the jmx.jar in the /(catalinahome)/bin I had to add this directory to the CLASSPATH variable in the catalina.sh script.
The second problem was a bug in /usr/bin/build-classpath command which is called from the catalina.sh script. At times, the command would append an error message to the CLASSPATH variable. Novell confirmed this bug. Their fix was to create a link for java-1 as follows: ln -s /etc/alternatives/java_sdk_exports /usr/lib64/jvm- exports/java-1 Both these problems I think are fixed in SP1. Aria On Thu, 30 Aug 2007 10:08:27 -0400 Mrohs, Ray said: >Hi, >We began testing Tomcat 5 a few weeks ago. It starts OK when I'm logged >in and I use '/etc/init.d/tomcat5 start'. However there is a problem >when starting during the boot process. From what I can tell in the logs, >it can't find jmx.jar which is normally part of the CLASSPATH >definition. I set CLASSPATH in profile.local. > >I tried running 'sh /etc/profile.local' after boot.local and before >Tomcat is supposed to start, but CLASSPATH still doesn't show up in env. >I tried starting Tomcat via Yast, chkconfig, and the above command from >my local /config setup, with the same result. I'm hoping there's a >simple answer to this? =20 > > > >Ray Mrohs >U.S. Department of Justice >202-307-6896 >=20 > >---------------------------------------------------------------------- >For LINUX-390 subscribe / signoff / archive access instructions, >send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit >http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
