Oracle Weblogic Server (MOSC)

MOSC Banner

Unable to start ohs1

edited May 13, 2024 8:32AM in Oracle Weblogic Server (MOSC) 6 commentsAnswered

When trying to start ohs1 getting below error,

Connecting to Node Manager ...
<May 13, 2024 8:07:23 AM UTC> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.>
<May 13, 2024 8:07:23 AM UTC> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<May 13, 2024 8:07:23 AM UTC> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>
Successfully Connected to Node Manager.
Starting server ohs1 ...
This Exception occurred at Mon May 13 08:09:26 UTC 2024.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center