Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#28986 - [tomcat7] TOMCAT_JAVA_HOME variable in /etc/conf.d/tomcat7 doesn't match installed Java version

Attached to Project: Arch Linux
Opened by Psycho McStabStab (Leave_This_Place) - Sunday, 18 March 2012, 03:00 GMT
Last edited by Guillaume ALAUX (galaux) - Saturday, 24 March 2012, 22:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Guillaume ALAUX (galaux)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

On starting Tomcat, the rc.d/tomcat7 script checks /etc/conf.d/tomcat7 for variables, including TOMCAT_JAVA_HOME. It chose Java 7 of the installed JDK/JRE, instead of checking which version of JDK/JRE was installed and JAVA_HOME is set to. In my case, TOMCAT_JAVA_HOME was set to /usr/lib/jvm/java-7-openjdk instead of the installed /usr/lib/jvm/java-6-openjdk.

Additional info:
tomcat7 7.0.25-1

/etc/conf.d/tomcat7

   tomcat7 (0.6 KiB)
This task depends upon

Closed by  Guillaume ALAUX (galaux)
Saturday, 24 March 2012, 22:03 GMT
Reason for closing:  Not a bug
Comment by Psycho McStabStab (Leave_This_Place) - Sunday, 18 March 2012, 15:28 GMT
Hello,

My mistake! the RELEASE_NOTES packaged in the stock release of Tomcat7 (which are not included with the repo version of Tomcat7) state that tomcat7 requires the NEWEST version of JRE/JDK. It took forever finding this, which could have been avoided had the RELEASE_NOTES been included in the /usr/share/tomcat7/ directory in the first place.
Comment by Guillaume ALAUX (galaux) - Saturday, 24 March 2012, 22:03 GMT
The reason why this tomcat7 init conf file uses "TOMCAT_JAVA_HOME=/usr/lib/jvm/java-7-openjdk" is just because JDK7 could now be considered as the default in Arch. I know this may be a big assumption but after all, jdk7-openjdk replaces openjdk6 in that they conflict with each other and jdk7-openjdk has a greater version number.
I introduced a /etc/profile.d/jdk.sh file in jdk7-openjdk that could have been useful in such case but unfortunately we have not added it in openjdk6 for compatibility reasons.

> My mistake! the RELEASE_NOTES ...
Then I close this case.

Loading...