Do they ever test their updates?
Jun. 20th, 2009 06:53 pmI have just updated my openSuSE 11.1 vmware image with the latest updates.
Guess what: Tomcat 6 does not even start any more. Again. Exactly the same as the last two times I updated.
Every time I update SuSE, tomcat breaks. *sigh*
Why? Because in /usr/bin/dtomcat6 the $JAVA_HOME variable is not set, which means that all it produces is
/bin/java no such file or directory
The offending line in the script is, "${JAVA_HOME}/bin/java". Which is correct if you set $JAVA_HOME, as you must if using java. But /etc/init.d/tomcat6 doesn't.
It is impossible to even start tomcat, the script bombs immediately. Which means the person who made this update package cannot possibly have tested it...
Guess what: Tomcat 6 does not even start any more. Again. Exactly the same as the last two times I updated.
Every time I update SuSE, tomcat breaks. *sigh*
Why? Because in /usr/bin/dtomcat6 the $JAVA_HOME variable is not set, which means that all it produces is
/bin/java no such file or directory
The offending line in the script is, "${JAVA_HOME}/bin/java". Which is correct if you set $JAVA_HOME, as you must if using java. But /etc/init.d/tomcat6 doesn't.
It is impossible to even start tomcat, the script bombs immediately. Which means the person who made this update package cannot possibly have tested it...