Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1089495

Summary:	Add support for Java 8 with JBoss ON 3.3.2 components
Product:	[JBoss] JBoss Operations Network	Reporter:	Heiko W. Rupp <hrupp>
Component:	Productization	Assignee:	Jirka Kremser <jkremser>
Status:	CLOSED ERRATA	QA Contact:	Filip Brychta <fbrychta>
Severity:	high	Docs Contact:
Priority:	high
Version:	JON 3.2	CC:	dmasirka, fbrychta, hrupp, jkremser, loleary, lzoubek, mfoley, miburman, myarboro
Target Milestone:	DR01	Keywords:	Triaged
Target Release:	JON 3.3.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1089473	Environment:
Last Closed:	2015-04-30 16:09:43 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1089473, 1208854
Bug Blocks:

Description Heiko W. Rupp 2014-04-19 20:11:45 UTC

We should make sure that JON runs on JDK8 as customers may want to use that and are more likely to move over when Java7 runs out of official support from Oracle.

This does not mean we should use any Java 8 features.


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

JDK 7 runs out of support in the middle of 2015, so we need to make sure early to support running on JDK 8, which has been released in March 2014 and starts to be the common runtime among Java shops.

Comment 2 Heiko W. Rupp 2014-08-13 19:00:35 UTC

Yes, *running* is the key here. Not compiling.

Comment 6 Larry O'Leary 2014-12-18 00:43:46 UTC

Please note that this BZ represents the task/enhancement of testing and validation of JVM 8. Any bugs or issues should be captured in separate BZs as blockers for this BZ.

Comment 8 Michael Burman 2015-01-13 22:26:05 UTC

Before shipping a product with these JDK8 enhancements, those PermGen error messages should be removed (even if harmless, they're not pretty and might cause confusion).

Comment 9 Jirka Kremser 2015-01-14 16:16:43 UTC

That would require modification of the start bash scripts and adding some conditions based on the Java version. Removing them wouldn't be wise, because when running with jdk 7 and lower it could crash with "OOM: PermGen space".

@Michael Burman
feel free to do that if you want it should be fairly easy [1]


[1]: http://stackoverflow.com/a/7335524/1594980

Comment 11 Jirka Kremser 2015-01-27 12:54:34 UTC

here is a 1liner I use on my box for removing the permgen options based on jdk version: https://gist.github.com/Jiri-Kremser/8bb0646a0010875beee9

Comment 13 Libor Zoubek 2015-03-23 09:44:47 UTC

Moving to ON_QA as there is nothing to chrerry-pick (per discussion with Jirka)

Comment 14 Libor Zoubek 2015-03-23 09:47:05 UTC

Sorry .. should have been moved to MODIFIED

Comment 15 Jirka Kremser 2015-03-23 10:09:36 UTC

You are right, for running on top of jdk8 there is nothing to cherry-pick. However, it could be hard to test without also building it on jdk8, because our i-tests in jenkins runs after the compilation phase.

Comment 17 Michael Burman 2015-03-27 10:56:06 UTC

These need to be documented I guess:

OpenJDK 64-Bit Server VM warning: ignoring option PermSize=128M; support was removed in 8.0
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=128M; support was removed in 8.0

Comment 19 Filip Brychta 2015-04-23 17:48:29 UTC

All testing is done and there is only one issue found bz1208854. This is IBM SDK specific issue which will be addressed in JON3.3.3

Comment 21 errata-xmlrpc 2015-04-30 16:09:43 UTC

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.

https://rhn.redhat.com/errata/RHSA-2015-0920.html