jsvc (from commons-daemon) still can't find a JVM: it statically looks
for jvm.cfg, then tries various well-known libjvm.so locations (but
unfortunately not the server one). It needs to be taught about that
one so that it can find it.
** Also affects: commons-daemon (Ubuntu)
Importance:
Hm, that will not be sufficient. Once jsvc is fixed, Tomcat finally needs the
following defined in java.security to start:
policy.expandProperties=true
policy.allowSystemProperty=true
And java.security is also a conffile, so this is also available only after
configuration. Not sure we have a
** Also affects: openjdk-6 (Ubuntu)
Importance: Undecided
Status: New
--
Tomcat 6 fails to start during install
https://bugs.launchpad.net/bugs/288616
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.
--
This bug was fixed in the package openjdk-6 - 6b14-0ubuntu3
---
openjdk-6 (6b14-0ubuntu3) jaunty; urgency=low
* Update IcedTea build infrastructure (20081217).
* Add support for PARISC.
* Use a default jvm.cfg if the jvm.cfg doesn't yet exist after unpacking
the runtime
Proposed patch.
java-common (0.30ubuntu5) jaunty; urgency=low
* Make default-jre-headless depend on both *-jre-headless and *-jre-lib,
except for gcj where it should just depend on java-gcj-compat-headless
(fixes LP: #288616)
** Attachment added: java-common_0.30ubuntu5.debdiff
The problem is not a pre-depend one but rather a circular dependency in
openjdk-6 (bug 291123) and sun-java6 (bug 291128). Those circular
dependencies are arbitrarily broken at some point and may result in
Tomcat trying to start while the JRE is not yet available...
** Changed in: tomcat6
