|
Problem |
When a customer is starting their application server, they
geting a 'socket closed exception' in their tracefile. The applications
functionality is not effected. |
|
Cause |
Customer gets the following exception in their tracefile
when starting an Application Server:
java.net.SocketException: Socket closed
at java.net.PlainSocketImpl.socketSetOption(Native Method)
at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:210)
at java.net.Socket.setKeepAlive(Socket.java:619)
at
com.ibm.CORBA.iiop.ConnectionTable.createSSLConnection(ConnectionTable.java:1232)
at com.ibm.CORBA.iiop.ConnectionTable.get(ConnectionTable.java:514)
at com.ibm.CORBA.iiop.GIOPImpl.locate(GIOPImpl.java:181)
at com.ibm.CORBA.iiop.ClientDelegate.is_a(ClientDelegate.java:1522)
at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:82)
at
com.ibm.rmi.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:262)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:146)
at
com.ibm.CORBA.services.lsd.LocationServiceClient.<init>(LocationServiceClient.java:140)
at
com.ibm.CORBA.services.lsd.LocationServiceClient.initialize(LocationServiceClient.java:161)
at
com.ibm.ejs.oa.LocationService.registerExplicit(LocationService.java:191)
at
com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:160)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:350)
at com.ibm.ws.runtime.Server.initializeOrb(Server.java:1457)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:941)
at
com.ibm.ejs.sm.server.ManagedServer.initializeRuntime0(ManagedServer.java:408)
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime0(AdminServer.java:1152)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:884)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:401)
at java.lang.reflect.Method.invoke(Native Method)
|
|
Solution |
This is fixed by The latest JSSE Cumulative Security Fixes
starting with the Mar 17, 2003 release. |
|
|
|
|
|
|