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

Zulu JDK 8 + TLS 1.3 support conflicts with Oracle JDK 8 /FISH-43 #4407

Closed
DeCaMil opened this issue Jan 3, 2020 · 2 comments
Closed

Zulu JDK 8 + TLS 1.3 support conflicts with Oracle JDK 8 /FISH-43 #4407

DeCaMil opened this issue Jan 3, 2020 · 2 comments
Assignees
Labels
Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev Type: Bug Label issue as a bug defect

Comments

@DeCaMil
Copy link

DeCaMil commented Jan 3, 2020

Description


Using Oracle JDK 8 u231 to run 5.194 fails because the Oracle JVM does not support the -XX:+UseOpenJSSE option introduced by PAYARA-3997.

The min/max versions work with widely supported features, but not with per-vendor features. Perhaps the min/max notation needs to be extended to [min|max|vendor]. With the |vendor being optional and it's absence implying all vendors.

Expected Outcome

Updating the Java installation by a patch level (u221 to u231) should not prevent instances from starting.

Current Outcome

The instance fails to start.

Steps to reproduce (Only for bug reports)

1 - Start the domain using Oracle Java 1.8.0 u231

C:\payara5> java -version
java version "1.8.0_231"
Java(TM) SE Runtime Environment (build 1.8.0_231-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.231-b11, mixed mode)

C:\payara5> bin\asadmin start-domain payaradomain

2 - Create a standalone instance

C:\payara> bin\asadmin create-instance test-instance

3 - Start the instance:

C:\payara5> bin\asadmin start-instance test-instance
remote failure: Could not start instance test-instance on node localhost-payaradomain (localhost).

Command failed on node localhost-payaradomain (localhost): CLI801 Instance is already synchronized
Attempting to start test-instance.... Please look at the server log for more details.....

To complete this operation run the following command locally on host localhost from the Payara Server install location C:\payara5:

    lib/nadmin  start-local-instance --node localhost-payaradomain --sync normal --timeout 120 test-instance
Command start-instance failed.

4 - Run the recommended command:
(The direction given is incorrect as there is no lib directory in the payara5 directory. It needs to be glassfish/lib/nadmin.)

C:\payara5> glassfish\lib\nadmin  start-local-instance --node localhost-payaradomain --sync normal --timeout 120 test-instance
Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
CLI801 Instance is already synchronized
Waiting for test-instance to start .Error starting instance test-instance.
The server exited prematurely with exit code 1.
Before it died, it produced the following output:

Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Unrecognized VM option 'UseOpenJSSE'

Command start-local-instance failed.

Environment

  • Payara Version: 5.194
  • Edition: Web
  • JDK Version: Oracle 1.8.0 u231
  • Operating System: Windows Server 2016
@rdebusscher rdebusscher self-assigned this Jan 6, 2020
@rdebusscher rdebusscher added the Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev label Jan 6, 2020
@rdebusscher
Copy link

Hi @DeCaMil,

We are aware of some problems related to the JVM option for the TLS 1.3 support and have already internal issue CUSTCOM-90 active for this.

I tried to reproduce your case with OpenJDK 8u232 but instance started successfully.

So you can either remove the option or add -XX:+IgnoreUnrecognizedVMOptions for the time being.

Regards
Rudy

@OndroMih OndroMih changed the title Zulu JDK 8 + TLS 1.3 support conflicts with Oracle JDK 8 Zulu JDK 8 + TLS 1.3 support conflicts with Oracle JDK 8 /CUSTCOM-90 Feb 4, 2020
@fturizo fturizo changed the title Zulu JDK 8 + TLS 1.3 support conflicts with Oracle JDK 8 /CUSTCOM-90 Zulu JDK 8 + TLS 1.3 support conflicts with Oracle JDK 8 /FISH-43 Nov 12, 2020
@fturizo fturizo added the Type: Bug Label issue as a bug defect label Nov 12, 2020
@MeroRai MeroRai assigned MeroRai and unassigned rdebusscher Nov 12, 2020
@MeroRai
Copy link
Member

MeroRai commented Nov 12, 2020

Hi @DeCaMil,

This issue should be fixed in the current release of the Payara Server Community edition.

Kind regards,
Mero

@MeroRai MeroRai closed this as completed Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev Type: Bug Label issue as a bug defect
Projects
None yet
Development

No branches or pull requests

4 participants