PQ90107: getByName() failure when tunneling with security enabled

 Fixes are available

5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for AIX
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for HP-UX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Linux
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for HP-UX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Solaris
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Windows
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Solaris
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Windows
5.0.2.7: WebSphere Application Server Express 5.0.2 Cumulative Fix 7
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Solaris
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Solaris
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Windows
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for AIX
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Linux
5.0.2.12: WebSphere Application Server 5.0.2 Cumulative Fix 12
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for HP-UX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for AIX
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.8: WebSphere Application Server V5.0.2 Cumulative Fix 8
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Windows
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Solaris
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Linux
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for HP-UX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for AIX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Windows
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Solaris
5.1.1.1: WebSphere Application Server Express 5.1.1 Cumulative Fix 1
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Windows
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for AIX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Linux
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for AIX
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Windows
5.0.2.13: WebSphere Application Server 5.0.2 Cumulative Fix 13
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for HP-UX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for AIX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Windows
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Linux
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for HP-UX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for HP-UX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for AIX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Linux
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Linux
5.1.1.1: WebSphere Application Server Version 5.1.1 Cumulative Fix 1
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for HP-UX



APAR status
Closed as program error.

Error description
In a tunneling scenario, the client app is not always be able
to resolve the hostname of app servers that lie within the
firewall. If the PROVIDER_URL of a client is not resolveable to
the client, the following error is thrown (even though the same
code works with security disabled):

 java.net.UnknownHostException: xxxxxxxxxx
 at java.net.InetAddress.getAllByName0(InetAddress.java:591)
 at java.net.InetAddress.getAllByName0(InetAddress.java:560)
 at java.net.InetAddress.getByName(InetAddress.java:469)
 at
com.ibm.CORBA.transport.TransportBase.getHostIPAddress(Transport
Base.jav
a:104)
 at
com.ibm.rmi.iiop.TransportManager.getHostIPAddress(TransportMana
ger.java
:175)
 at com.ibm.rmi.Profile.getHostIPAddress(Profile.java:405)
 at
com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterc
eptor$2.
run(SecurityConnectionInterceptor.java:1316)
 at java.security.AccessController.doPrivileged(Native Method)
 at
com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterc
eptor.ge
tConnectionKey(SecurityConnectionInterceptor.java:1312)
 at
com.ibm.ws.orbimpl.transport.WSTransport.getConnection(Unknown
Source)
 at
com.ibm.CORBA.transport.TransportBase.getConnection(TransportBas
e.java:1
58)
 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:2929)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitC
txFactor
y.java:1256)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(Ws
nInitCtx
Factory.java:1107)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServe
r(WsnIni
tCtxFactory.java:679)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnI
nitCtxFa
ctory.java:607)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextIntern
al(WsnIn
itCtxFactory.java:482)
 at
com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:102
)
 at
com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.ja
va:408)
 at
com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:131)
 at javax.naming.InitialContext.lookup(InitialContext.java:359)
 at
lda.client.AtFaultService.instantiateEjb(AtFaultService.java:352
)
 at
lda.client.AtFaultService.initService(AtFaultService.java:307)
 at java.lang.reflect.Method.invoke(Native Method)
 at lda.client.AtFaultService.dispatch(AtFaultService.java:130)
 at lda.client.AtFaultService.main(AtFaultService.java:390)
Local fix
Add the hostname of the unresolvable host to the hosts file of
the client
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who are   *
*                 enabling HTTP tunneling with a firewall.     *
****************************************************************
* PROBLEM DESCRIPTION: In a tunneling scenario, the client     *
*                      app is not always be able to resolve    *
*                      the hostname of application servers     *
*                      that are behind the firewall. If the    *
*                      PROVIDER_URL of a client is not         *
*                      resolveable to the client,              *
*                      java.net.UnknownHostException           *
*                      exception is thrown.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In a tunneling scenario, the client app is not always be able
to resolve the hostname of app servers that lie within the
firewall. If the PROVIDER_URL of a client is not resolveable to
the client, the following error is thrown (even though the same
code works with security disabled):

 java.net.UnknownHostException: xxxxxxxxxx
 at java.net.InetAddress.getAllByName0(InetAddress.java:591)
 at java.net.InetAddress.getAllByName0(InetAddress.java:560)
 at java.net.InetAddress.getByName(InetAddress.java:469)

The reason is an attempt is made to resolve the hostname to an
IP address.
Problem conclusion
If the IP address cannot be resolve, the hostname is now used
instead.
Temporary fix
Sent a test fix to customer
Comments
APAR information
APAR number PQ90107
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-06-14
Closed date 2004-06-29
Last modified date 2004-06-29

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Publications Referenced

Fix information

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


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ90107
IBM Group: Software Group
Modified date: Jun 29, 2004