Fix (APAR):  PK73716Status:  FixRelease:  6.1.0.19,6.1.0.17,6.1.0.15,6.0.2.31,6.0.2.29,6.0.2.27,6.0.2.23Operating System:  AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,WindowsSupersedes Fixes:  CMVC Defect:  PK73716Byte size of APAR:  54813Date: 2008-11-18Abstract:  Service Connector Architecture (SCA) applications begin executing inbound work before the server is started.Description/symptom of problem:  PK73716 resolves the following problem:ERROR DESCRIPTION:?                                             When individual applications start, any inbound J2EE Connector  Architecture (JCA) work can be immediately processed by the     server even if dependent servers or applications have not yet   started. A common symptom of this behavior is that a            NameNotFoundException occurs due to the fact that a dependent   application has not yet started.                                LOCAL FIX:?                                                     NA                                                              PROBLEM SUMMARY:?USERS AFFECTED: WebSphere Process Server users.PROBLEM DESCRIPTION:Service Connector Architecture (SCA)applications begin executing inboundwork before the server is started.RECOMMENDATION:NoneWhen individual Service Connector Architecture applicationsstart, inbound work may start executing on the server beforedependent applications and servers are started and readyto process work.  A common symptom of this behavior is aNameNotFoundException that occurs whenever a dependentapplication has not yet started.PROBLEM CONCLUSION:?                                            APAR PK73716 delays the server from executing inbound work      until sufficient resources are available.  In particular, the   server does not activate message endpoints until all            applications are started.                                                                                                       The fix for this APAR is currently targeted for inclusion in    WebSphere Process Server fixpacks 6.0.2.6 and 6.1.2.2; and      WebSphere Application Server fixpacks 6.0.2.33, 6.1.0.23 and    7.0.0.3. 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 to2) The Editions that apply3) Delete the Editions & Methods that do not apply and this NoteFix applies to Editions:Release 6.0__ Application Server (Express or BASE)__ 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__ BothNOTE: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 <was_root>/updateinstaller/version.txt.The Update Installer can be downloaded from the following link:http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991For detailed instructions to Extract the Update Installer see the following Technote:http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205400Note 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 WebSphereManually 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-IFPK12345CDirections 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 FIXExample: 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 WebSphereManually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.2) Start Update Installer3) 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 WebSphereDirections to re-apply fix:  1) Shutdown WebSphere.2) Follow the Fix instructions to apply the fix.3) Restart WebSphere.Additional Information: