Fix (APAR): PK23985 Status: Fix Release: 6.0.2.7, 6.0.2.9, 6.0.2.11 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PK23985 Byte size of APAR: 16 KB Date: 2006-08-10 Abstract: Running ./addNode.sh with option -includeapps results in too many open files. Description/symptom of problem: PK23985 resolves the following problem: ERROR DESCRIPTION: Errors similar to following will be seen in the Deployment Manager SystemOut.log WKSP0018E: Error reading file for cells/Cell1/applications/Edit page _and layout_PA_1_0_39.ear/Edit page _and layout_PA_1_0_39.ear --java.io.IOException: The system cannot find the specified file, either the filename is too long on Windows system or run out of file descriptor on UNIX platform. java.io.FileNotFoundException: C:\wps\profiles\NDMGR\wstemp\addNode1142956396562\workspace\cell s\Cell1\ applications\Edit page _and layout_PA_1_0_39.ear\Edit page _and layout_PA_1_0_39.ear (Too many open files) Errors similar to the following will be displayed in the in the addnode.log [3/22/06 9:58:08:734 CST] 0000000a SOAPConnector < handleAdminFault Exit javax.management.MBeanException: null nested exception is com.ibm.websphere.management.exception.ConfigServiceException: WKSP0018E Error read file for cells/Cell1/applications/FileServer_PA_1_0_4H.ear/deltas/FileSer ver_PA_1 _0_4H.ear/delta-1139163900312 --java.io.IOException: The system cannot find the specified file, either the filename is too long on Windows system or run out of file descriptor on UNIX platform. java.io.FileNotFoundException: C:\wps\profiles\NDMGR\wstemp\addNode1143043024875\workspace\cell s\Cell1\ applications\FileServer_PA_1_0_4H.ear\deltas\FileServer_PA_1_0_4 H.ear\de lta-1139163900312 (Too many open files) LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server users of version 6.0.2. PROBLEM DESCRIPTION: Running ./addNode.sh with option -includeapps results in too many open files. RECOMMENDATION: None Running the addNode command with -includeapps throws java.io.FileNotFoundException with too many open files error message. This happens due to the large number of files in the workspace which are to be synched with the Master Repository. DocumentContentSource encapsulates FileInputStream for every document in the workspace which needs to be synched up with the Master Repository. When there are a large number of files to be synched up, a large number of open file handles are created which is shown as a java.io. FileNotFoundException : too many open files error message PROBLEM CONCLUSION: New logic was implemented whereby the FileInputStream are opened only when the file is about to be updated to the Master Repository thereby preventing too many parallel FileInputStream handles. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.13 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: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Network Deployment (ND) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ 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.0.2.2 or newer of the Update Installer. 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-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to 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 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) 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) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 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: