Fixes are available
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
On Windows7, when the ORB attempts to create a new outgoing connection and one of the endpoints (client or server) is the loopback address ("localhost") and the other resolves to an external nic (e.g. 9.76.159.242), a SocketException can occur.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * versions 7.0, and 8.0. * **************************************************************** * PROBLEM DESCRIPTION: When an ORB tries to create a TCP * * connection to a WebSphere server it * * can fail with a SocketException: * * Network is unreachable * **************************************************************** * RECOMMENDATION: * **************************************************************** The original reported problem occurred when a WebSphere AppServer attempted to create an Object Request Broker (ORB) connection back to a wsadmin client. Here a System Management handleNotifications() callback failed with the following exception: [11/4/11 18:27:10:092 CET] 00000024 ORBRas 1 com.ibm.ws.orbimpl.transport.WSTCPTransportConnection connect:403 Non-deferrable Alarm : 1 The following exception was logged java.net.SocketException: Network is unreachable: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:383) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:2 45) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:232) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377) at java.net.Socket.connect(Socket.java:539) at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSock et(WSTCPTransportConnection.java:395) at com.ibm.CORBA.transport.TransportConnectionBase.connect(Transpor tConnectionBase.java:356) ... at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.j ava:1308) at com.ibm.rmi.corba.ClientDelegate.request(ClientDelegate.java:188 4) at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDelegate.java:12 64) at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:458) at com.ibm.ws.management.connector.rmi._RMINotificationListener_Stu b.handleNotifications(_RMINotificationListener_Stub.java:40) ... at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1650) ALL the following conditions must exist in order to experience this problem: -- Client (this could be a server acting as a client) is on Windows7 or Windows 2008 R2 -- ORB_LISTENER_ADDRESS host value (in serverindex.xml): If client has an internal address of "localhost" or "127.0.0.1" and the server has an external IP address or host name (for example, 147.10.32.117). OR client has an external address and server has internal address "localhost". -- client ORB property com.ibm.CORBA.ConnectTimeout > 0 -- client ORB property com.ibm.ws.orb.transport.useMultiHome=true The code handling the creation of a TCP socket does not correctly handle the case where useMultiHome=true (do not bind to a single network address) and ConnectTimeout>0. It errantly tries to bind the socket to the single address given in com.ibm.CORBA.LocalHost, which for Windows7 always results in a SocketException if going external to internal or internal to external. NOTE: On Windows7 and Windows 2008 R2, even with this fix, if useMultiHome=false, and the client attempts to create a connection which goes from an external address to an internal server address ("localhost"), or an internal client address to an external server address, the same SocketException will occur. Microsoft's statement on this behavior is as follows: "This is working as designed. The Windows networking stack does not forward packets across different scope zones. The loopback and public interfaces are in different scope zones which is why we cannot workaround this by enabling the Weak Host Model."
Problem conclusion
In the case where the com.ibm.CORBA.ConnectTimeout property > 0, there was no check for the value of com.ibm.ws.orb.transport.useMultiHome and the code errantly did a socket.bind to the client's ORB_LISTENER_ADDRESS, The fix added a code block to handle the case where useMultiHome=true, in which case no socket.bind will be performed. The fix for this APAR is ‚  currently targeted for inclusion in fixpacks 7.0.0.23 and 8.0.0.3 Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM57797
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-09
Closed date
2012-04-16
Last modified date
2012-04-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
28 October 2021