Not Able To Access EM Console Or WLS Console After Setting Up SOA CS Domain With Custom Identity And Custom Trust
(Doc ID 2356169.1)
Last updated on AUGUST 12, 2024
Applies to:
SOA Suite Cloud Service - Version N/A and laterInformation in this document applies to any platform.
Symptoms
After configuring SOA CS environment with custom Identity and Trust, EM or WLS console are not accessible. Looking at the standard out log of Admin server, the server is not listening on SSL Port and reports the error. Issue occurs only when the instance started through myservices console. If the server started directly through startWebLogic.sh, then both the console(s) are accessible.
ERROR
-----------------------
<Jan 23, 2018, 5:12:57,144 PM UTC> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
<Jan 23, 2018, 5:12:57,145 PM UTC> <Alert> <Security> <BEA-090717> <Invalid server CLOUD_adminserver SSL configuration>
..........
<Jan 23, 2018, 5:14:32,506 PM UTC> <Error> <Server> <BEA-002606> <The server is unable to create a server socket for listening on channel "DefaultSecure[iiops]". The address xx.xxx.xxx.xxx might be incorrect or another process is using port 9072: java.io.IOException: Invalid server CLOUD_adminserver SSL configuration>
......
and server is not listening on SSL port (7002)
<Jan 23, 2018, 5:14:32,514 PM UTC> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on xx.xxx.xxx.xxx:9071 for protocols iiop, t3, ldap, snmp, http.>
<Jan 23, 2018, 5:14:32,514 PM UTC> <Notice> <Server> <BEA-002613> <Channel "ExternAdmin" is now listening on xx.xxx.xxx.xxx:7001 for protocols t3, http.>
<Jan 23, 2018, 5:14:32,517 PM UTC> <Notice> <Server> <BEA-002613> <Channel "channel-dep" is now listening on xx.xxx.xxx.xxx:9001 for protocols t3, http.>
<Jan 23, 2018, 5:14:32,518 PM UTC> <Notice> <WebLogicServer> <BEA-000329> <Started the WebLogic Server Administration Server "CLOUD_adminserver" for domain "CLOUD_domain" running in production mode.>
<Jan 23, 2018, 5:14:32,518 PM UTC> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on xx.xxx.xxx.xxx:9071 for protocols iiop, t3, ldap, snmp, http.>
<Jan 23, 2018, 5:14:32,518 PM UTC> <Notice> <Server> <BEA-002613> <Channel "ExternAdmin" is now listening on xx.xxx.xxx.xxx:7001 for protocols t3, http.>
<Jan 23, 2018, 5:14:32,518 PM UTC> <Notice> <Server> <BEA-002613> <Channel "channel-dep" is now listening on xx.xxx.xxx.xxx:9001 for protocols t3, http.>
<Jan 23, 2018, 5:14:32,521 PM UTC> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>
<Jan 23, 2018, 5:14:33,426 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>
<Jan 23, 2018, 5:20:28,99 PM UTC> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=CLOUD_server_1 :
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Add a custom identity and trust to SOA CS Environment.
2. Restart admin server and access EM or WLS Console.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |