Bug 1232827

Summary: [RFE] Provide java 8 in OpenShift Enterprise
Product: OpenShift Container Platform Reporter: Ricardo Martinelli de Oliveira <rmartine>
Component: ContainersAssignee: Timothy Williams <tiwillia>
Status: CLOSED ERRATA QA Contact: libra bugs <libra-bugs>
Severity: urgent Docs Contact:
Priority: high    
Version: 2.2.0CC: adellape, anli, jialiu, jkaur, jokerman, libra-onpremise-devel, mmccomas, nicholas_schuetz, pep, rhowe, tiwillia, xiama
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift-origin-cartridge-jbosseap-2.26.3.1-1.el6op Doc Type: Enhancement
Doc Text:
This enhancement updates the JBoss EAP cartridge to allow the usage of Java 8, which can be used by adding the "java8" marker.
Story Points: ---
Clone Of:
: 1233268 (view as bug list) Environment:
Last Closed: 2015-09-30 16:37:58 UTC Type: Bug
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:    
Bug Blocks: 1233268    

Description Ricardo Martinelli de Oliveira 2015-06-17 15:05:03 UTC
Description of problem:
Create a java8 marker to use with JBoss EAP 6. Since EAP 6.3.3 java8 is supported.

Version-Release number of selected component (if applicable):
OpenShift Enterprise 2.2

Comment 2 Josep 'Pep' Turro Mauri 2015-06-29 08:49:31 UTC
*** Bug 1233268 has been marked as a duplicate of this bug. ***

Comment 3 Jaspreet Kaur 2015-06-29 09:14:01 UTC
Hello,

 EAP 6.4 officially supports java8 and  JDK 1.8 is also available in RHEL6. Can you please update when this could be available in Openshift 2.2.

Regards,
Jaspreet

Comment 7 openshift-github-bot 2015-07-31 14:04:02 UTC
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/c28b3871c7cade7fd1585d881cb8a3418f6cf996
Include java-1.8 openjdk to support java8 in jbosseap

Bug 1232827
https://bugzilla.redhat.com/show_bug.cgi?id=1232827
To use the java8 marker introduced by 632d56c8cca60207504c5323301825e03aecb5fd, the java-1.8.0-openjdk packages will be required.

Comment 17 Anping Li 2015-09-18 06:43:00 UTC
The fix wasn't in the puddle, we need another puddle.

Comment 19 Ma xiaoqiang 2015-09-22 05:56:30 UTC
Check on puddle [2.2.7/2015-09.21.1]

1. create jbossews-1.0, jbossews-2.0, jbosseap app
2. rename java7 to java8
3. deploy the app
4. check the process and env
#rhc app ssh $app_name
> ps -ef
>env|grep JAVA

the jbosseap app works fine
[jbp-xiaom.ose22-auto.com.cn xiaom-jbp-1]\> env|grep JAVA
JAVA_HOME=/etc/alternatives/java_sdk_1.8.0
[jbp-xiaom.ose22-auto.com.cn xiaom-jbp-1]\> ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
2899     15232     1  0 13:37 ?        00:00:00 /usr/bin/logshifter -tag jbosseap
2899     15233     1  0 13:37 ?        00:00:00 /bin/sh /var/lib/openshift/xiaom-jbp-1/jbosseap//bin/standalone.sh
2899     15571 15233  2 13:37 ?        00:00:21 /etc/alternatives/java_sdk_1.8.0/bin/java -D[Standalone] -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms40m
2899     23519 23507  0 13:50 ?        00:00:00 sshd: xiaom-jbp-1@pts/0
2899     23520 23519  0 13:50 pts/0    00:00:00 /bin/bash --init-file /usr/bin/rhcsh -i
2899     25130 23520  0 13:53 pts/0    00:00:00 ps -ef

the jbossews apps can not switch to java8.

Comment 20 Timothy Williams 2015-09-22 14:09:51 UTC
I should have specified, the only jboss application that supports java 8 is the jbosseap application. The jbossews application cannot support java 8 due to using jbossews-2.0. A jbossews-3.0 cartridge would support java 8, but there are no plans to create a jbossews-3.0 cartridge.

Comment 21 Ma xiaoqiang 2015-09-23 07:01:22 UTC
check on puddle [2.2.7/2015-09.22.1]

jbosseap works fine.

Comment 23 errata-xmlrpc 2015-09-30 16:37:58 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-1844.html