A fix is available
APAR status
Closed as program error.
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.<init>(Socket.java:335) at java.net.Socket.<init>(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: * **************************************************************** 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
Temporary fix
Comments
APAR Information
APAR number
PK53569
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-09-26
Closed date
2007-09-26
Last modified date
2007-09-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
SDK
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 October 2021