Troubleshooting
Problem
Attempts to refresh node status in WebSphere Application Server Integrated Solutions Console are unsuccessful. This technote also applies to On-Premise product.
Symptom
Node is unreachable from the Deployment Manager. Starting node manager results in the following error:
[7/31/17 9:32:54:783 GMT] 00000095 ORBRas E com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl createSSLSocket ProcessDiscovery : 0 JSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: Server chose TLSv1, but that protocol version is not enabled or not supported by the client. javax.net.ssl.SSLHandshakeException: Server chose TLSv1, but that protocol version is not enabled or not supported by the client.
at com.ibm.jsse2.bb.a(bb.java:225)
at com.ibm.jsse2.bb.a(bb.java:500)
at com.ibm.jsse2.ab.t(ab.java:74)
at com.ibm.jsse2.ab.a(ab.java:137)
at com.ibm.jsse2.qc.a(qc.java:421)
at com.ibm.jsse2.qc.h(qc.java:428)
at com.ibm.jsse2.qc.a(qc.java:813)
at com.ibm.jsse2.qc.startHandshake(qc.java:636)
at com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl.performSSLHandshakeAndGetSession(WSSSLClientSocketFactoryImpl.java:458)
at com.ibm.ws.security.orbssl.WSSSLClientSocketFactoryImpl.createSSLSocket(WSSSLClientSocketFactoryImpl.java:210)
at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection.createSocket(WSSSLTransportConnection.java:236)
at com.ibm.ws.orbimpl.transport.WSSSLTransportConnection.createSocket(WSSSLTransportConnection.java:315)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:350)
at com.ibm.ws.orbimpl.transport.WSTransport$1.run(WSTransport.java:503)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:500)
at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:181)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:97)
at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:134)
Cause
Node configuration is invalid.
Resolving The Problem
Verify Deployment Manager configuration for itself and all nodes; open Integrated Solutions Console and navigate to:
SSL certificate and key management > SSL configurations >
<choose dmgr/node> Quality of protection (QoP) settings > General properties > Protocol
Nodes must have the same setting as Deployment Manager. Once settings are updated, synchronize node settings by navigating to the affected node and run the following command:
syncNode <HOST> <SOAP_CONNECTOR_ADDRESS"> -stopservers -restart
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22006759