openjdk team mailing list archive
-
openjdk team
-
Mailing list archive
-
Message #01667
[Bug 288616] Re: Packages depending on JRE might not have a usable JRE when configured
So it can't be fixed by just working around it in commons-daemon. We need the JRE to be fully installed before it's put in use. Solutions left include:
1- PreDepend
2- Fix apt
3- Make default-jre-headless depend on both openjdk6-lib and openjdk6-jre-headless
Reopening tasks for apt and java-common, since I'm still unsure why (3) isn't the easiest solution.
** Summary changed:
- Tomcat 6 fails to start during install
+ Packages depending on JRE might not have a usable JRE when configured
** Changed in: commons-daemon (Ubuntu)
Assignee: Thierry Carrez (ttx) => (unassigned)
Status: Confirmed => Invalid
** Changed in: java-common (Ubuntu)
Status: Invalid => New
** Changed in: commons-daemon (Ubuntu Intrepid)
Status: New => Invalid
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
Packages depending on JRE might not have a usable JRE when configured
https://bugs.launchpad.net/bugs/288616
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in ubuntu.
Status in “apt” source package in Ubuntu: New
Status in “commons-daemon” source package in Ubuntu: Invalid
Status in “java-common” source package in Ubuntu: New
Status in “openjdk-6” source package in Ubuntu: Fix Released
Status in “tomcat6” source package in Ubuntu: Invalid
Status in apt in Ubuntu Intrepid: New
Status in commons-daemon in Ubuntu Intrepid: Invalid
Status in java-common in Ubuntu Intrepid: Invalid
Status in openjdk-6 in Ubuntu Intrepid: New
Status in tomcat6 in Ubuntu Intrepid: Invalid
Bug description:
Binary package hint: tomcat6
In some cases Tomcat 6 fails to successfully start *during install*. This doesn't prevent the installation from succeeding and you can still run "sudo service tomcat6 start" to start it once it is installed.
If a JRE is not completely configured by the time Tomcat is started, Tomcat will fail to start. This can happen in some installation scenarios as Tomcat 6 doesn't formally "pre-depend" on a JRE.
For example, on a minimal system, the packages seem to be configured in that order (some lines removed for clarity):
$ sudo apt-get install tomcat6 tomcat6-examples tomcat6-admin tomcat6-user
Setting up default-jre-headless (1.6-30ubuntu3) ...
Setting up openjdk-6-jre-lib (6b12-0ubuntu4) ...
Setting up tomcat6 (6.0.18-0ubuntu3) ...
* Starting Tomcat servlet engine tomcat6 ...fail!
Setting up openjdk-6-jre-headless (6b12-0ubuntu4) ...
However if you run:
$ sudo apt-get install tomcat6
Setting up openjdk-6-jre-lib (6b12-0ubuntu4) ...
Setting up default-jre-headless (1.6-30ubuntu3) ...
Setting up openjdk-6-jre-headless (6b12-0ubuntu4) ...
Setting up tomcat6 (6.0.18-0ubuntu3) ...
* Starting Tomcat servlet engine tomcat6 [OK]