[jaunty] openjdk-6 update broke rmid

[Steve Beattie]

With openjdk-6-jre-headless=6b14-1.4.1-0ubuntu13 installed, the Java RMI Activation System Daemon rmid fails to start with a NullPointerException, like so:

$ rmid -J-Dsun.rmi.activation.execPolicy=none
Activation.main: an exception occurred: java.io.IOException: log recover failed with exception: java.lang.NullPointerException
java.io.IOException: log recover failed with exception: java.lang.NullPointerException
 at sun.rmi.log.ReliableLog.recover(ReliableLog.java:226)
 at sun.rmi.server.Activation.startActivation(Activation.java:218)
 at sun.rmi.server.Activation.main(Activation.java:2057)

Using the version originally released with jaunty, openjdk-6-jre-headless=6b14-1.4.1-0ubuntu7, rmid starts successfully as invoked above.

This failure causes several of the TCK runtime tests to fail.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: openjdk-6-jre-headless 6b14-1.4.1-0ubuntu13
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: openjdk-6
Uname: Linux 2.6.28-19-generic i686
UnreportableReason: This is not a genuine Ubuntu package

[Steve Beattie (sbeattie)]

It looks like it was the last update, 6b14-1.4.1-0ubuntu13, that broke rmid, as the rmid in the openjdk-6-jre-headless package from https://launchpad.net/ubuntu/jaunty/+source/openjdk-6/6b14-1.4.1-0ubuntu12 starts succeesfully (as well as the 6b14-1.4.1-0ubuntu11 and 6b14-0ubuntu10 versions).

[Matthias Klose (doko)]

built updated packages without hardening defaulgs, http://people.canonical.com/~doko/tmp/6b18-lucid-nh
rmid starts for me with these.

[Matthias Klose (doko)]

otoh, I think we didn't enable hardening in jaunty in openjdk

[Steve Beattie (sbeattie)]

Matthias, this problem *only* exists in openjdk 6b14-1.4.1-0ubuntu13 as published in jaunty-updates; I can confirm that rmid starts up without problem from the version of openjdk in the openjdk ppa, 6b18~pre4-1ubuntu1~jaunty2. Whatever is causing this failure is strictly brought on by the changes in http://launchpadlibrarian.net/43320995/openjdk-6_6b14-1.4.1-0ubuntu12_6b14-1.4.1-0ubuntu13.diff.gz .
I generated this bug report to record why I could not use the current jaunty version in generating a baseline for regression testing (and to have it available in case others ran across the issue).

Please don't disable the hardening defaults pre-emptively. It is quite likely that the update to 6b18 as necessitated by the firefox 3.6.6 update will address the issue as a side effect. Sorry for the confusion.

[Steve Beattie (sbeattie)]

Oh, and also in the interest of clarity, I do not see the issue with the version in karmic-updates (6b16-1.6.1-3ubuntu3), lucid (6b18-1.8-0ubuntu1), or the version you rebuilt for lucid with ant from lucid-proposed.

Thanks.

[Steve Beattie (sbeattie)]

Now that it is built, I can confirm that the rmid included in the version of openjdk-6 in the ubuntu-mozilla-security ppa, 6b18-1.8-0ubuntu1~9.04.2, also starts successfully.

[Matthias Klose (doko)]

afaiu this is fixed with the 6b18-1.8 update in jaunty

[Steve Beattie (sbeattie)]

On Tue, Jul 27, 2010 at 03:14:09PM -0000, Matthias Klose wrote:
> afaiu this is fixed with the 6b18-1.8 update in jaunty

Yes, confirmed that this has been fixed with the update to jaunty.
Thanks!

--
Steve Beattie
<email address hidden>
http://NxNW.org/~steve/