Bug 1456505

Summary:	(6.4.z) JBMAR-190 - Using internal JDK classes causes issues on recent JDK9 builds
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Petr Penicka <ppenicka>
Component:	Remoting	Assignee:	Petr Jurak <pjurak>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiří Bílek <jbilek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	bmaxwell, david.lloyd, jbilek, pjurak, rstancel
Target Milestone:	CR1
Target Release:	EAP 6.4.17
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-06 13:32:11 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:	1450092, 1456926

Description Petr Penicka 2017-05-29 13:36:39 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Petr Penicka 2017-05-29 13:52:47 UTC

Description from JIRA:

sun.reflect.ReflectionFactory.newConstructorForSerialization() signature changed in recent JDK9 in incompatible way.
So code running on JDK8 using that method won't run on JDK9 anymore without appropriate actions taken.

Comment 4 Jiří Bílek 2017-08-03 14:57:19 UTC

According to code revision the fix is included.
Verified with EAP 6.4.17.CP.CR3

Comment 5 Petr Penicka 2017-09-06 13:32:11 UTC

Released on 2017-09-05 as part of the EAP 6.4.17 release.