Fix (APAR): PK53569 Status: Fix Release: 6.1.0.9,6.1.0.11 Operating System: AIX,HP-UX,Linux,Linux pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 4 Date: 2007-10-01 Abstract: Socket connect exceptions during meta callbacks Description/symptom of problem: PK53569 resolves the following problem: ERROR DESCRIPTION: Error Message: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused: connect:host=localHost,port=2954 Stack Trace: Server side Exception org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused: connect:host=localHost,port=2954 vmcid: IBM minor code: E02 completed: No at com.ibm.CORBA.transport.TransportConnectionBase.connect(Transpor tConnectionBase.java:450) at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTranspo rt.java:437) at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBas e.java:162) at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:81) at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:182) at com.ibm.rmi.corba.ClientDelegate.locate(ClientDelegate.java:1938 ) at com.ibm.rmi.corba.ClientDelegate._createRequest(ClientDelegate.j ava:1963) at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.ja va:1143) at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.ja va:1225) at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.j ava:1287) at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.ja va:1121) at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.j ava:1253) at com.ibm.rmi.corba.ClientDelegate.request(ClientDelegate.java:184 1) at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDelegate.java:12 09) at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:460) at com.ibm.org.omg.SendingContext._CodeBaseStub.meta(_CodeBaseStub. java:115) at com.ibm.rmi.iiop.FVDCodeBaseDelegate.meta(FVDCodeBaseDelegate.ja va:145) at com.ibm.rmi.io.IIOPInputStream.inputObjectFVD(IIOPInputStream.ja va:1407) at com.ibm.rmi.io.IIOPInputStream.readSerializable(IIOPInputStream. java:1032) at com.ibm.rmi.io.IIOPInputStream.simpleReadObjectInternal(IIOPInpu tStream.java:317) at com.ibm.rmi.io.IIOPInputStream.simpleReadObject(IIOPInputStream. java:347) at com.ibm.rmi.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java: 200) at com.ibm.rmi.iiop.CDRInputStream.read_value(CDRInputStream.java:1 961) at com.ibm.tws.conn.engine._EJSRemoteStatelessConnEngine_da67e2e1_T ie.getEngineInfo(_EJSRemoteStatelessConnEngine_da67e2e1_Tie.java :157) at com.ibm.tws.conn.engine._EJSRemoteStatelessConnEngine_da67e2e1_T ie._invoke(_EJSRemoteStatelessConnEngine_da67e2e1_Tie.java:89) at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDe legate.java:610) at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:4 63) at com.ibm.rmi.iiop.ORB.process(ORB.java:439) at com.ibm.CORBA.iiop.ORB.process(ORB.java:1737) at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2350) at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2195) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:65) at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1470) Caused by: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:336) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:2 01) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:188) at java.net.Socket.connect(Socket.java:478) at java.net.Socket.connect(Socket.java:428) at java.net.Socket.(Socket.java:335) at java.net.Socket.(Socket.java:150) at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSock et(WSTCPTransportConnection.java:308) at com.ibm.CORBA.transport.TransportConnectionBase.connect(Transpor tConnectionBase.java:376) ... 33 more Client Side Exception Trace from server: 1198777258 at host fmossot5.dyn.webahead.ibm.com >> org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : initial and forwarded IOR inaccessible vmcid: IBM minor code: 89A completed: No at com.ibm.rmi.iiop.CDRInputStream.read_value(CDRInputStream.java:1 968) at com.ibm.tws.conn.engine._EJSRemoteStatelessConnEngine_da67e2e1_T ie.getEngineInfo(_EJSRemoteStatelessConnEngine_da67e2e1_Tie.java :157) at com.ibm.tws.conn.engine._EJSRemoteStatelessConnEngine_da67e2e1_T ie._invoke(_EJSRemoteStatelessConnEngine_da67e2e1_Tie.java:89) at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDe legate.java:610) at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:4 63) at com.ibm.rmi.iiop.ORB.process(ORB.java:439) at com.ibm.CORBA.iiop.ORB.process(ORB.java:1737) at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2350) at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2195) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:65) at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code)) << END server: 1198777258 at host fmossot5.dyn.webahead.ibm.com . LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: IBM WebSphere Application Server version 6.1 users PROBLEM DESCRIPTION: Socket connect exceptions during meta callbacks RECOMMENDATION: None The problem is seen when a class be passed as a argument or return value during rmi-iiop communication has a structural differences on client and server sides. In this case the server will call back the client or vice versa to obtain the meta information about the class. This can result is a new connection being created by server back to the client. When there is a firewall running on the client machine it will block the incoming connection. There are problems seen when the client is running on a VPN connection. The problem can even happen if the com.ibm.CORBA.LocalHost property is set to an unreachable address on the client side. PROBLEM CONCLUSION: This defect will be fixed in: 5.0.0 SR6 1.4.2 SR9 . The client can specify the com.ibm.CORBA.enableClientCallbacks property so that some additional context information would be included in the SendingContextRuntime IOR which is used for callbacks. The Server will understand this context and will use the same incoming connection to make outgoing meta callbacks. For this to work this apar is required to be installed on both client as well as the server side. . To obtain the fix: Install build 20070525 or later Directions to apply fix: Fix applies to Editions: Release 6.1 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes _X_ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: This iFix is for SDK 1.5 SR5 ONLY