I installed the Debian wheezy net install dated December 8th, 2011, for AMD-64,
and selected the 'SSH Server' option during install.
I then executed the commad:
$ sudo apt-get install openjdk-7-jdk openjdk-7-jre-headless
Which appeared to complete without error.
I then executed the command
$ sudo apt-get install tomcat6
Which failed in the tomcat6 initscript:
Selecting previously unselected package tomcat6.
Unpacking tomcat6 (from .../tomcat6_6.0.32-7_all.deb) ...
Processing triggers for man-db ...
Setting up authbind (1.2.0) ...
Setting up libcommons-pool-java (1.5.6-1) ...
Setting up libcommons-dbcp-java (1.4-2) ...
Setting up libecj-java (3.5.1-3) ...
Setting up libgeronimo-jta-1.1-spec-java (1.1.1-2) ...
Setting up libservlet2.5-java (6.0.32-7) ...
Setting up libtomcat6-java (6.0.32-7) ...
Setting up tomcat6-common (6.0.32-7) ...
Setting up tomcat6 (6.0.32-7) ...
Creating config file /etc/default/tomcat6 with new version
Adding system user `tomcat6' (UID 105) ...
Adding new user `tomcat6' (UID 105) with group `tomcat6' ...
Not creating home directory `/usr/share/tomcat6'.
no JDK found - please set JAVA_HOME ... failed!
invoke-rc.d: initscript tomcat6, action "start" failed.
If I edit '/etc/default/tomcat6' to specify my JAVA_HOME as
'/usr/lib/jvm/java-1.7.0-openjdk-amd64' the tomcat6 init script is able to run
The tomcat6 initscript checks a hard-coded list of jvm paths, and the location
of my openjdk-7 installation is not among them.
Of interest, the tomcat7 init script checks first for
'/usr/lib/jvm/default-java', but that wouldn't have helped since the openjdk-7
installation doesn't create that path. So presumably this bug would also apply
to tomcat7, but I have not tested that.
This is the maintainer address of Debian's Java team
debian-j...@lists.debian.org for discussions and questions.