Bug 1484399 - [GSS] [OpenJDK] The JVM option ExitOnOutOfMemoryError has been removed when upgrading to 1.7.0_141
[GSS] [OpenJDK] The JVM option ExitOnOutOfMemoryError has been removed when u...
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: java-1.7.0-openjdk (Show other bugs)
Unspecified Linux
unspecified Severity high
: rc
: ---
Assigned To: Andrew John Hughes
Lukas Zachar
Depends On:
  Show dependency treegraph
Reported: 2017-08-23 08:55 EDT by Francesco Marchioni
Modified: 2018-04-10 13:37 EDT (History)
4 users (show)

See Also:
Fixed In Version: java-1.7.0-openjdk-
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-04-10 13:35:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Icedtea Bugzilla 3465 None None None 2017-10-10 12:46 EDT
openjdk bug system JDK-8138745 None None None 2017-09-08 13:14 EDT
Red Hat Product Errata RHBA-2018:0944 None None None 2018-04-10 13:37 EDT

  None (edit)
Description Francesco Marchioni 2017-08-23 08:55:04 EDT
Description of problem:
The option ExitOnOutOfMemoryError is no longer available since upgrading from openjdk 1.7.0_131 to 1.7.0_141.
There is no clue from the release notes why this option has been removed.
On the other hand, the option is available in  java-1.8.0-openjdk-devel.x86_64

Version-Release number of selected component (if applicable):
Openjdk 1.7.0_141

How reproducible:
By installing RPM packages as follows:

yum install java-1.7.0-openjdk-devel.x86_64
java -XX:+ExitOnOutOfMemoryError -version
Unrecognized VM option 'ExitOnOutOfMemoryError'

Expected results:
java version "1.7.0_141"

Additional info:

The option works with OpenJDK8:
yum install java-1.8.0-openjdk-devel.x86_64
java -XX:+ExitOnOutOfMemoryError -version
java version "1.8.0_60"
Comment 2 Deepak Bhole 2017-08-23 16:57:42 EDT
Andrew, do you know if this is intentional?
Comment 3 jiri vanek 2017-08-24 10:24:54 EDT
It probably can be returned, but only as  rpm specific patch (==not recommended) as:

$ java -X
    -Xmixed           mixed mode execution (default)
                      show all locale related settings and continue

The -X options are non-standard and subject to change without notice.

I tasys it all.... Sorry.
Comment 5 Andrew John Hughes 2017-09-08 13:14:35 EDT
There seems to be some confusion here. I can see no evidence that -XX:+ExitOnOutOfMemoryError has ever been present in java-1.7.0-openjdk.

It was added to OpenJDK 8 in u92:

8138745: Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot
Reviewed-by: dholmes
Contributed-by: cheleswer.sahu@oracle.com

It has never been backported to OpenJDK 7.

The bug confusingly lists it as being in 7u101 and 7u111, but this is a reference to Oracle's proprietary JDK updates (java-1.7.0-oracle)

8138745 is a fairly simple fix, so we could consider backporting it as well. Generally, we've only backported changes going into 8u that have been part of security updates (odd-numbered releases such as 8u91 and 8u141), and not feature updates such as 8u92. I do have an ongoing TODO to look over the Oracle 7u updates for other changes, but it's lower priority than the security updates and ongoing RHEL requests for fixes for both 7 & 8.

Francesco, would it make it easier for you to have this option available in OpenJDK 7?
Comment 7 Andrew John Hughes 2017-10-10 12:46:35 EDT
Scheduled for inclusion in the next upstream release, given its already in the proprietary 7 version and has no effect unless one of the new options is enabled.
Comment 13 errata-xmlrpc 2018-04-10 13:35:37 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.