APAR status
Closed as program error.
Error description
WebSphere throws the following error during remote ORB
communication after applying
PQ83268 or 5.0.2.5:
14:46:39.649
com.ibm.ws.orbimpl.transport.WSTCPTransportConnection
connect:448 P=590573:O=0:CT ORBRas[default]
java.net.SocketException: errno: 126, error: Cannot assign
requested address for fd: 10
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:1
37)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124)
at java.net.Socket.<init>(Socket.java:268)
at java.net.Socket.<init>(Socket.java:147)
at
com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSock
et(WSTCPTransportConnection.java:221)
at
com.ibm.CORBA.transport.TransportConnectionBase.createSocket(Tra
nsportConnectionBase.java:650)
at
com.ibm.CORBA.transport.TransportConnectionBase.connect(Transpor
tConnectionBase.java:410)
at
com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTranspo
rt.java:416)
at
com.ibm.CORBA.transport.TransportBase.getConnection(TransportBas
e.java:158)
at
com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:83)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:174)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:305)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:367)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:2938)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitC
txFactory.java:1256)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(Ws
nInitCtxFactory.java:1107)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServe
r(WsnInitCtxFactory.java:679)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnI
nitCtxFactory.java:607)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextIntern
al(WsnInitCtxFactory.java:482)
at
com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:102
)
at com.ibm.ws.naming.util.WsnInitCtx.<init>(WsnInitCtx.java:82)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnIn
itCtxFactory.java:327)
at
com.ibm.websphere.naming.WsnInitialContextFactory.getInitialCont
ext(WsnInitialContextFactory.java:112)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.j
ava:660)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.jav
a:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at
com.ibm.websphere.naming.DumpNameSpace.getStartingContext(DumpNa
meSpace.java:397)
at
com.ibm.websphere.naming.DumpNameSpace.main(DumpNameSpace.java:3
19)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
Local fix
Uninstalling 5.0.2.5 or
PQ83628 allows the remote ORB
communication to work without problems
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server multiple NIC *
* users during remote ORB communications. *
****************************************************************
* PROBLEM DESCRIPTION: Users with multiple NICs may receive a *
* java.net.SocketException during remote *
* ORB calls. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
One branch of the createSocket() method is missing the handing
of multiple NICs information. A socket creation down this path
will attempt to create the socket on all NICs at all times.
Problem conclusion
createSocket() is fixed to handle the multiple NIC card
property 'useMultiHome' correctly in this path.
The fix for this problem is available in 5.1.0.5 (and higher)
and 5.0.2.6 (and higher).
Temporary fix Comments
APAR information |
APAR number |
PQ88152 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
003 |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-04-28 |
Closed date |
2004-11-10 |
Last modified date |
2004-11-10 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|