Fix (APAR): JR25291 Status: Fix Release: 6.0.1.4,6.0.1.3,6.0.1.2 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: FIX (APAR): JR25291 SUPERSEDES FIXES: JR24190 CMVC Defect: JR25291 Byte size of APAR: 39943 Date: 2007-02-06 Abstract: Binary not get copied to all nodes while deploying application to dynamic cluster via console. Description/symptom of problem: JR25291 resolves the following problem: ERROR DESCRIPTION: The problem was that the applications were not being expanded in the correct location after an application install. This was because the tasklist that AppBinaryProcessor maintains did not have the task that does this function. com.ibm.ws.sca.internal.deployment.SCATaskProvider was being added to the list as one of the extensions. This initialization process never finished and the thread was hung. This left the task list incomplete and caused problems downstream LOCAL FIX: none, manual copy PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.1.x Network Dispatch Users with Portal Server. PROBLEM DESCRIPTION: Binary not get copied to all nodes while deploying application to dynamic cluster via console. RECOMMENDATION: Use the iFix JR25291 The applications were not being expanded in the correct location after an application install. This was because the tasklist that AppBinaryProcessor maintains did not have the task that does this function. com.ibm.ws.sca.internal.deployment.SCATaskProvider was being added to the list as one of the extensions. This initialization process never finished and the thread was hung. This left the task list incomplete and caused problems downstream. PROBLEM CONCLUSION: Made corresponding changes in ALConfig.java of ArtifactLoaderImpl package. Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system. Also download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server Additional Information: