Fix (APAR): JR32145 Status: Fix Release: 6.0.2.5,6.0.2.4 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 9563 Date: 2009-04-13 Abstract: When the serviceDeployTask fails, it does not set the failOnError return code correctly, which means that ANT does not detect that the serviceDeployTask failed. Description/symptom of problem: JR32145 resolves the following problem: ERROR DESCRIPTION: The ws_ant(.bat or .sh) expects to be passed a build file that defines tasks and passes parameters to them: See Ref: http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/topic/c om.ibm.websphere.wesb.doc/doc/tdep_usingant.html This example actually shows how to call the ServiceDeploy task. The issue here is that the ws_ant script is NOT returning the error code back to the calling program (which could be another program or script). It is absolutely critical that an accurate error code is returned so that user can detect errors.Looking further into the problem, ws_ant actually starts java to run a headless eclipse and calls the ant tasks from there.The problem is that java is not returning any error when there are errors. Here is a trace that will clearly illustrate the problem: [INFO] C:\WorkSpaces\SCT\IS6_ManageWorkOrder\IS6_CON_WorkOrder\IS6_CON_ WO_EA \target>call \sct\Programs\WID602\runtimes\bi_v6\bin\ws_ant.bat -buildfile C:\tmp\was6plugin-build.xml servicedeploy [INFO] Buildfile: C:\tmp\was6plugin-build.xml [INFO] [INFO] servicedeploy: [INFO] [servicedeploy] Starting workbench in C:\tmp\11f63cc7e9e [INFO] [servicedeploy] Initializing workspace [INFO] [servicedeploy] No such archive: C:/SCT/Libs/Custom/TelstraCustom-3.0.0.1.jar [INFO] [servicedeploy] Deployment failed [INFO] [servicedeploy] Waiting for background jobs [INFO] [servicedeploy] Deleting workspace [ERROR] [servicedeploy] Java Result: 2 [INFO] [INFO] BUILD SUCCESSFUL [INFO] Total time: 15 seconds [INFO] ws_ant error level = 0 [INFO] Error Level = 0 [INFO] Return code: 0 A Java Result of anything other than zero is considered an error. However, the ws_ant error level is zero, which is what java is returning (so eclipse is not setting the error code correctly and it is not being returned). LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server v6.x and Enterprise Service Bus v6.x users of the serviceDeploy ANT task. PROBLEM DESCRIPTION: When the serviceDeployTask fails, it does not set the failOnError return code correctly, which means that ANT does not detect that the serviceDeployTask failed. RECOMMENDATION: None The serviceDeployTask was incorrectly setting the failOnError value to the same as the ignoreOnErrors value. This caused the serviceDeployTask to not fail on error by default, and to fail on error when ignoreErrors was set to true. This is the opposite of the correct behavior. PROBLEM CONCLUSION: The code was changed to set the value of failOnError to be the opposite of the ignoreOnErrors value, which means that by default the serviceDeployTask will fail on errors, and return the correct return code to ANT. This fix is targeted for future Websphere Process Server v6.0.2, v6.1, v6.1.2, and v6.2 fixpacks. Directions to apply fix: 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 Process Server. 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 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. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Process Server. 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: