Bug#405851: Daemon fails to start with all JVMs; this is serious

Loïc Minier lool at dooz.org
Wed May 16 20:32:14 UTC 2007


severity 405851 serious
tags 405851 + confirmed
stop

        Hi,

 While verifying whether #356066 was fixed, I was also greeted with:
Adding system user `jetty' (UID 119) ...
Adding new user `jetty' (UID 119) with group `nogroup' ...
Not creating home directory `/usr/share/jetty'.
Could not start Jetty servlet engine because no Java Development Kit
(JDK) was found. Please download and install JDK 1.3 or higher and set
JAVA_HOME in /etc/default/jetty to the JDK's installation directory.

 But I have gcj, java-1.5.0-sun-1.5.0.11, and java-6-sun-1.6.0.00...

java - status is auto.
 link currently points to /usr/lib/jvm/java-gcj/jre/bin/java
/usr/lib/jvm/java-1.5.0-sun/jre/bin/java - priority 53
 slave java.1.gz: /usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/man/man1/java.1.gz
/usr/lib/jvm/java-6-sun/jre/bin/java - priority 63
 slave java.1.gz: /usr/lib/jvm/java-6-sun-1.6.0.00/jre/man/man1/java.1.gz
/usr/bin/gij-4.1 - priority 41
/usr/lib/jvm/java-gcj/jre/bin/java - priority 1041
Current `best' version is /usr/lib/jvm/java-gcj/jre/bin/java.

 So, I'm bumping the severity as jetty fails to start with any JVMs.

   Bye,
-- 
Loïc Minier




More information about the pkg-java-maintainers mailing list