Fix (APAR): PK29976 Status: Fix Release: 6.0.2.11 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: PK29976 Byte size of APAR: 73629 Date: 2006-08-21 Abstract: A potential synchronization issue may arise when two or more EJB jars in the same EAR are accessed at about the same time. Description/symptom of problem: PK29976 resolves the following problem: ERROR DESCRIPTION: When there are two or more EJB Jars in the same EAR there is the potential to encounter a synchronization issue because. the EJB Jar files are beneath a common parent, simultaneous calls to different EJB Jar files can result in simultaneous calls to trieve the deployment descriptor of the shared parent EAR. Concurrent access to EJBs is causing concurrent access through to application data. An example of the exception seen in the log file: EJBContainerI E WSVR0068E: Attempt to start EnterpriseBean MyBean#MyEJB.jar#Mytest failed with exception: com.ibm.etools.j2ee.commonarchivecore.exception. DeploymentDescriptorLoadException: META-INF/application.xml !Stack_trace_of_nested_exce! com.ibm.etools.j2ee.commonarchivecore. exception.EmptyResourceException: META-INF/application.xml LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Service users on versions 6.0.2.x and 6.1.0.x PROBLEM DESCRIPTION: A potential synchronization issue may arise when two or more EJB jars in the same EAR are accessed at about the same time. RECOMMENDATION: None When there are two or more EJB Jars in the same EAR, and at least two or more are being accessed at roughly the same time, there is the potential to encounter a synchronization issue. This issue can arise because the EJB Jar files are beneath a common parent and thus simultaneous calls may be made to retrieve the deployment descriptor of the shared parent EAR. Concurrent access to EJBs is causing concurrent access through to application data. An example of the exception seen in the log file: EJBContainerI E WSVR0068E: Attempt to start EnterpriseBean MyEar#MyEJB.jar#MyTestBean failed with exception: com.ibm.etools.j2ee.commonarchivecore.exception. DeploymentDescriptorLoadException: META-INF/application.xml !Stack_trace_of_nested_exce! com.ibm.etools.j2ee.commonarchivecore. exception.EmptyResourceException: META-INF/application.xml PROBLEM CONCLUSION: This fix provided the code necessary to avoid the synchronization issues described above. The fix for this APAR is currently targeted for inclusion in fixpacks 6.0.2.17 and 6.1.0.4. 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 _X_ 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 _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.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 6.0.2.11-WS-WAS-IFPK29976.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 (6.0.2.11-WS-WAS-IFPK29976.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 (6.0.2.11-WS-WAS-IFPK29976.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: