Hi All,
After making a change (com.ibm.ssl.verifyHostname = false) from websphere admin console , the BAW server is no longer starting. Although we have reverted the change in the backend security.xml files at the following paths:
…the DMGR still fails to start. We also attempted a VM reboot, but the issue persists.
Change:
A custom property was added via the WebSphere Admin Console:
Security > SSL certificate and key management > SSL Configurations >
IHUBMQSSLSettings > Custom properties > com.ibm.ssl.verifyHostname = false
Observations:
Logs at the time of failure:
CWSCF0002I: The client code is attempting to load the security configuration from the server and this operation is not allowed.
JSAS0006I: Security connection interceptor initialized.
JSAS0001I: Security configuration initialized.
JSAS0003I: Authentication mechanism: BASICAUTH
Connection Exception:
javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:dmgrhost:9809/WsnAdminNameService"
Root exception: java.net.ConnectException: Connection refused (127.0.0.1:9809)
During DMGR Startup:
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization.
Appreciate your help!!
Thanks,
Venkat
------------------------------
Venkat Miriyala
------------------------------