Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FISH 6027 - Remote EJB + JDK 17 does not work #5664

Merged
merged 1 commit into from
Mar 23, 2022

Conversation

JamesHillyard
Copy link
Member

@JamesHillyard JamesHillyard commented Mar 18, 2022

Description

These changes do not fix remote EJBs on JDK 17 directly, the suggested fix for this is to specify --add-opens=java.base/java.lang=ALL-UNNAMED to the invoking command as short of refactoring the IllegalReflectiveAccess there is no fix to this (See JIRA for more information)

These changes instead specify this --add-opens to the remote-ejb-tracing sample which I identified is also broken due to this error.
These changes also add the parameter -Dorg.glassfish.gmbal.no.multipleUpperBoundsException=true to the GlassFishORBManager meaning it doesn't need to be specified by the client. This issue is explained here: eclipse-ee4j/orb-gmbal#22

Important Info

Blockers

None

Testing

New tests

None

Testing Performed

Manually tested the fix against the reproducer in the community bug, my own reproducer and the remote-ejb-tracing sample. Tested the sample on JDK 8 to confirm the profile only activates on JDK 17+

Testing Environment

Windows 10, Zulu JDK 17 / Zulu JDK 8, Maven 3.6.3

Documentation

No documentation for Payara 6

Notes for Reviewers

Commit be90757 is cleaning up whitespace and fixing consistency within the GlassFishORBManager file and should be filtered out when reviewing changes.

FISH 6027 - Remote EJB + JDK 17 does not work
@JamesHillyard JamesHillyard merged commit e48aef5 into payara:Payara6 Mar 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants