GlassFish Server Fails to Start After New Server Certificate Added / Imported into KeyStore
(Doc ID 1288346.1)
Last updated on MARCH 12, 2021
Applies to:Oracle GlassFish Server - Version 2.1 and later
Information in this document applies to any platform.
GlassFish Server 2.x (Developer/Cluster profile) does not start up after a Private key is imported into the GlassFish Server 2.x keystore. The following errors are seen inside the GlassFish server.log and the server fails to start.
This new private key "<alias-name>" has a different password for it's key than the keystore's store password when it is imported from some other keystore.
2. Alternatively, the above error may also happen if an "asadmin change-master-password" is made
and the GlassFish keystore contains other application related private keys.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document