RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1450471 - Running JDKs are affected by moving JVM installation directories
Summary: Running JDKs are affected by moving JVM installation directories
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: java-1.8.0-openjdk
Version: 6.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Andrew John Hughes
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On: 1319875
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-12 17:05 UTC by Andrew John Hughes
Modified: 2017-12-06 10:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1319875
Environment:
Last Closed: 2017-12-06 10:44:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CentOS 9088 0 None None None 2017-05-12 17:05:22 UTC
Icedtea Bugzilla 2888 0 None None None 2017-05-12 17:05:22 UTC

Description Andrew John Hughes 2017-05-12 17:05:22 UTC 
This has now been fixed in RHEL 7. We should fix it in RHEL 6 too.

+++ This bug was initially created as a clone of Bug #1319875 +++

If the JDK is updated while an instance of the JVM is running, the JVM can lose access to files it needs to use, as the updated JVM is installed in a differently named directory, due to the changed Name-Version-Release triple (NVR).

This is particularly noticeable with the cacerts database, as it is loaded multiple times (see bug 8129988: JSSE should create a single instance of the cacerts KeyStore [0]). If a running JVM tries to load the cacerts file after a JDK update, the old cacerts file will no longer exist as it is referenced as java.home/jre/lib/security/cacerts, where java.home includes the full NVR.
This is visible in the CentOS bug, 9088.

As cacerts is actually just a symlink to /etc/pki/java/cacerts, we could fix the JDK to look to this location first, in the same way that the default.sf2 symlink was replaced by direct access to the soundfont [2].

We can try proposing this to upstream OpenJDK as well, but, given their reactions to doing a similar thing with the timezone database, it seems unlikely it would be accepted, so this may have to be kept as a local fix, at least until S8129988 is fixed.

[0] https://bugs.openjdk.java.net/browse/JDK-8129988
[1] https://bugs.centos.org/view.php?id=9088
[2] https://bugs.openjdk.java.net/browse/JDK-8140620
Comment 3 Jan Kurik 2017-12-06 10:44:04 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.