Fix (APAR): PK99773 Status: Fix Release: 6.1.0.27,6.1.0.25,6.1.0.23 Operating System: AIX,HP-UX,IBM i,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 100677 Date: 2009-11-30 Abstract: The IPv6 address might be truncated upon remote EJB call. Description/symptom of problem: PK99773 resolves the following problem: ERROR DESCRIPTION: An EJB client that tries to connect to the WAS server fails to bind its service to the JNDI initial context, and it also fails to lookup an EJB remote home from the initial context if the associated JNDI provider URL contains a literal IPv6 address. The format of the address is: : java.naming.provider.url=iiop://[1111:2:333:44:5555:6666:77:888] :2809 It seems that while processing the hostname part (1111:2:333:44:5555:6666:77:888), the last part of the address (:888) is split off (maybe being interpreted as a port number), and the remaining corrupted address (1111:2:333:44:5555:6666:77) cannot be contacted. Analysis of the orb trace shows that the request fails because of a truncated ipv6 address passed to the ORB by WAS sec code. java.net.UnknownHostException: 1111:2:333:44:5555:6666:77 at java.net.InetAddress.getAllByName0(InetAddress.java:1252) at java.net.InetAddress.getAllByName(InetAddress.java:1174) at java.net.InetAddress.getAllByName(InetAddress.java:1097) at java.net.InetAddress.getByName(InetAddress.java:1047) at com.ibm.CORBA.transport.TransportBase.getHostIPAddress(Transport Base.java:133) at com.ibm.rmi.iiop.TransportManager.getHostIPAddress(TransportMana ger.java:187) at com.ibm.rmi.Profile.getHostIPAddress(Profile.java:476) at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterc eptor.getHostfromProfile(SecurityConnectionInterceptor.java:2980 ) at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterc eptor.getConnectionKeyForLocateRequest(SecurityConnectionInterce ptor.java:1610) at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterc eptor.getConnectionKey(SecurityConnectionInterceptor.java:1440) at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTranspo rt.java:286) LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: All users of IBM WebSphere Application Server PROBLEM DESCRIPTION: The IPv6 address might be truncated upon remote EJB call. RECOMMENDATION: None Due to luck of IPv6 address consideration, IPv6 address is truncated when a client is accessing a remote security server. As a result, java.net.UnknownHostException is caught and an EJB invocation is failed. PROBLEM CONCLUSION: With this fix, the IPv6 no longer be truncated. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.31 and 7.0.0.9. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: Fix applies to Editions: Release 6.1 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) _X_ Application Client Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes _X_ Both For WebSphere Application Server, please use 6.1.0.23-WS-WAS-IFPK99773.pak. For WebSphere J2EE and Thin Client, please use 6.1.0.23-WS-AppClient-IFPK99773.pak. For WebSphere Admin Client, please use 6.1.0.23-WS-AppClient-IFPK99773A.pak. For WebSphere WebServices client, please use 6.1.0.23-WS-AppClient-IFPK99773W.pak. 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.1.0.13 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. 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.ibm.com/support/docview.wss?rs=180&uid=swg21205400 Note that there are two different methods for delivering iFixes, depending on the contents. The fix may be delivered either as a single file with a .pak extension (such as 6.1.0.11-WS-WAS-IFPK12345.pak) or a single file with a .zip extension (such as 6.1.0.11-WS-WAS-IFPK12345.zip) which then contains one or more files with a .pak extension. 1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into 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 and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. 8) Please note that in the future, if a Feature Pack is installed or uninstalled, a different set of iFixes will be needed. Use the Update Installer again at that time, with the maintenance directory location where these maintenance packages are stored, to determine the required interim fixes for the new WebSphere and Feature Pack(s) combination. 9) The maintenance packages could have one of a set of names, and these names will help determine which maintenance package you need to install. The APAR name (PKxxxxx) should appear as part of the filename. Between the APAR number and the .pak extension there will be 0 to 2 characters added. The table below indicates the usage of each of the maintenance packages with respect to which Feature Packs, if any, are installed. |.pak File Names |No Feature Packs|EJB3 Only|WebServices Only| Both | |6.1.0.x-WS-WAS-IFPK12345 | X | X | X | X | |6.1.0.x-WS-WAS-IFPK12345C | X | | | | |6.1.0.x-WS-WAS-IFPK12345CE | | X | X | X | |6.1.0.x-WS-WAS-IFPK12345W | X | X | | | |6.1.0.x-WS-WAS-IFPK12345WE | | | X | X | |6.1.0.x-WS-WAS-IFPK12345E | X | | X | | |6.1.0.x-WS-WAS-IFPK12345EE | | X | | X | 10) 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) Select file name of the maintenance package to uninstall (for example, 6.1.0.11-WS-WAS-IFPK12345.pak). 6) Verify the Uninstallation Summary and continue with the uninstall. 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: