Fix (APAR): PK84726 Status: Fix Release: 6.1.0.21 Operating System: Windows Supersedes Fixes: CMVC Defect: PK84726 Byte size of APAR: 19014 Date: 2009-05-12 Abstract: If wsadmin.bat is used without the -host parameter, a SOAPException may be seen. Description/symptom of problem: PK84726 resolves the following problem: ERROR DESCRIPTION: The customer doesn't necessary need to use the ipaddress. They just can not use anything that maps back to the loop back local ipadress: 127.0.0.1. But an actual host name should work for example: myserver.com. The actual problem is an Windows OS level issue in which the WebSphere Application Server, server socket gets prematurely terminated. This is not a wsadmin issue since it's the actual WebSphere server that experiences the premature socket termination. LOCAL FIX: We have noticed that this problem occurs when installing large applications. There is an easy test and work around to see if this is the same problem. Do not run the wsadmin in local mode, and when launching wsadmin use the -host option and the IP Address of the server to connect to. For example: wsadmin.bat -user userName -password password -host Alternatively, you can edit the com.ibm.ws.scripting.host property in wsadmin.properties with the IP address; for example: com.ibm.ws.scripting.host=xx.xx.xx.xx PROBLEM SUMMARY USERS AFFECTED: All users of IBM WebSphere Application Server version 6.1 on a Microsoft Windows operating system. PROBLEM DESCRIPTION: If wsadmin.bat is used without the -host parameter, a SOAPException may be seen. RECOMMENDATION: None If wsadmin.bat is used without the -host parameter, a SOAPException like the following may be seen: [SOAPException: faultCode=SOAP-ENV:Protocol; msg=Premature end of stream. Data is truncated. Read 99620 bytes successfully, expected 111240] PROBLEM CONCLUSION: Code is modified such that if the -host parameter is not specified (it is the loopback address), then the system property com.ibm.ws.http.waitBeforeCloseTime is consulted. The system property is the number of milliseconds to wait, after the read request completes, before closing the socket. The default is 10. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.27. 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 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) ___ WebSphere Business Integration Server Foundation (WBISF) ___ Edge Components ___ Developer ___ Extended Deployment (XD) Install Fix to: Method: ___ Application Server Nodes ___ Deployment Manager Nodes _x_ Both 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: