|
Problem |
Client application to server connection works properly on
WebSphere V4.0 to V4.0 and from V5.0 to V5.0. Client connections failed
for WebSphere V4.0 client to V5.0 server.
Stack traces showed following messages:
Ý14.08.03 03:02:59:514 CEST¨ 515445 ORBRas X
com.ibm.CORBA.iiop.IIOPConnection send(IIOPOutputStream, OneWay)
RM1:ldapmon The following exception was logged
java.io.IOException: Socket Closed
at java.net.PlainSocketImpl.getOutputStream(PlainSocketImpl.java:487)
at java.net.Socket$2.run(Socket.java:350)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.Socket.getOutputStream(Socket.java:347)
at com.ibm.sslite.bb.a(bb.java)
at com.ibm.sslite.k.a(k.java)
at com.ibm.sslite.l.<init>(l.java)
at com.ibm.sslite.bb.a(bb.java)
at com.ibm.sslite.bb.<init>(bb.java)
at com.ibm.jsse.bd.a(Unknown Source)
at com.ibm.jsse.b.a(Unknown Source)
at com.ibm.jsse.b.write(Unknown Source)
at com.ibm.CORBA.iiop.CommTraceOS.writeTo(CommTraceOS.java:88)
at com.ibm.CORBA.iiop.IIOPConnection.send(IIOPConnection.java:1428)
at com.ibm.CORBA.iiop.IIOPConnection.locate(IIOPConnection.java:1834)
at com.ibm.CORBA.iiop.GIOPImpl.locate(GIOPImpl.java:194)
at
com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1070
ORB and JSSE traces shows that the reason for the Socket being closed is
because of a
"unknown certificate" error. |
|
Cause |
In this case WebSphere's default dummykey files were being
used on both servers. WebSphere V5.0 is using a new, different, set of
self-signed certificates than is being used in the 4.0 version. |
|
Solution |
Export the certificate from the WebSphere V5.0 server's
DummyServerKeyfile.jks and import the certificate into the WebSphere's
V4.0 DummyServerTrustfile.jks, DummyClientKeyfile.jks and
DummyClientTrustfile.jks.
NOTE: It is NEVER recommended to use the default key files in
production environments.
See the infocenter for further information on using the Ikeyman tool
for creating and editing keyring files.
|
|
|
|
|
|
|