|
Problem(Abstract) |
After enabling Global Security, syncNode fails. Everything
works fine without security but it fails when security is enabled with the
below given exceptions
[5/24/05 0:57:37:207 CEST] 175b59 SOAPConnector
< reconnect [SOAPException: faultCode=SOAP-ENV:Client;
msg=Error opening socket: javax.net.ssl.SSLException:
Received fatal alert: handshake_failure (no cipher suites in common);
targetException=java.lang.IllegalArgumentException: Error opening
socket: javax.net.ssl.SSLException: Received fatal alert:
handshake_failure (no cipher suites in common)]
at org.apache.soap.transport.http.
SOAPHTTPConnection.send(Unknown Source)
at org.apache.soap.rpc.Call.invoke
(Unknown Source)
at com.ibm.ws.management.connector.
soap.SOAPConnectorClient$2.run(SOAPConnectorClient.java:245)
at java.security.AccessController.doPrivileged(Native Method)
[5/24/05 0:57:37:208 CEST] 175b59 AdminClientFa
< createAdminClient - failed
java.lang.reflect.InvocationTargetException:
com.ibm.websphere.management.exception.
ConnectorNotAvailableException
at com.ibm.ws.management.connector.soap.
SOAPConnectorClient.reconnect(SOAPConnectorClient.java:262)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.
<init>(SOAPConnectorClient.java:195)
at java.lang.reflect.Constructor.newInstance(Native Method)
---- Begin backtrace for nested exception
[SOAPException: faultCode=SOAP-ENV:Client;
msg=Error opening socket: javax.net.ssl.SSLException:
Received fatal alert: handshake_failure (no cipher suites in common);
targetException=java.lang.IllegalArgumentException:
Error opening socket: javax.net.ssl.SSLException:
Received fatal alert: handshake_failure (no cipher suites in common)]
at org.apache.soap.transport.http.
SOAPHTTPConnection.send(Unknown Source)
at org.apache.soap.rpc.Call.invoke(Unknown Source)
at com.ibm.ws.management.connector.soap.
SOAPConnectorClient$2.run(SOAPConnectorClient.java:245)
at java.security.AccessController.doPrivileged(Native Method)
Cont...
|
|
|
|
Cause |
The highly probable cause for this exception; there are
third party JAAS provider jars in the classpath (eg:
<WAS_HOME>/java/lre/lib/ext), The classes from these jars are
getting loaded first and interfering with IBM® version of JAAS
modules |
|
|
Resolving the
problem |
These directories should not have any third party classes
present in them. They will interfere with the functionality of the
product. Search your classpath and remove any third party jaas.jar files
you have in them.
If you need these third party jars for your application functionality
it is highly recommended to create a shared library for these jars and map
your application to them
|
|
|