Fix (APAR): PK36422 Status: Fix Release: 6.0.2.9 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: PK36422 Byte size of APAR: 35932 Date: 2007-01-15 Abstract: Error messages TUNE0407E, TUNE0408E, or TUNE0409E seen during server operations. Description/symptom of problem: PK36422 resolves the following problem: ERROR DESCRIPTION: Errors are seen in the systemout.logs during application server startup. Such as: - TUNE0409E: could not get server.xml resource from config root. TUNE0408E: Could not refresh TraceService Configuration TUNE0407E: Could not refresh repository cache ServerRuleDri E perfalert.Exception.errorjava.security. PrivilegedActionException: java.lang.NullPointer - TUNE0409E: could not get node.xml resource from config root - Trace.lgo shows: SystemErr R java.util.ConcurrentModificationException at org.eclipse.emf.common.util.BasicEList$EIterator. checkModCount (BasicEList.java(Inlined Compiled Code)) or SystemErr R org.eclipse.emf.common.util. BasicEList$BasicIndexOutOfBoundsException: index=0, size=0 at org.eclipse.emf.common.util.BasicEList.get (BasicEList.java (Compiled Code)) LOCAL FIX: I-fix available Search Keywords: Performance Auto-tuning Support WCV PROBLEM SUMMARY USERS AFFECTED: Users of WebSphere Application Server version 6. PROBLEM DESCRIPTION: Error messages TUNE0407E, TUNE0408E, or TUNE0409E seen during server operations. RECOMMENDATION: None The symptoms of this problem are the presence of error messages TUNE0407E, TUNE0408E, or TUNE0409E in the application server SystemOut.log, and the presence of a ConcurrentModificationException in the application server SystemErr.log log file. This particular problem was seen by a customer with a cell having more than 20 servers performing server startup. However, the problem may occur in other circumstances. For example: SystemErr.log 06/10/02 14:13:40:432 JST 0000003f SystemErr R java.util.ConcurrentModificationException at org.eclipse.emf.common.util.BasicEList$EIterator. checkModCount(BasicEList.java(Inlined Compiled Code)) at org.eclipse.emf.common.util.BasicEList$EIterator. next(BasicEList.java(Compiled Code)) ... lines omitted ... PROBLEM CONCLUSION: An ifix was created for WebSphere Application Server 6.0.2.13 through 6.0.2.17. Fix code was integrated into the WebSphere Application Server service pack level 6.0.2.19 and 6.1.0.7, and into the current development release. 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: Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) Install Fix to: __ 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 6.0.2.13-WS-WAS-IFPK36422.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.13-WS-WAS-IFPK36422.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.13-WS-WAS-IFPK36422.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: This ifix is for 6.0.2.13 through 6.0.2.17, inclusive.