Fix (APAR): PK57386 Status: Fix Release: 6.1.0.13 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: PK47882;PK56398 CMVC Defect: 478059 Byte size of APAR: 81893 Date: 2007-12-17 Abstract: No way to control the level of messages during server startup. Description/symptom of problem: PK57386 resolves the following problem: ERROR DESCRIPTION: There are so many warning messages that have little value during normal startup that it is easy to miss valid problems. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: IBM WebSphere Application Server version 6.1.0.15 users of web services. PROBLEM DESCRIPTION: No way to control the level of messages during server startup. RECOMMENDATION: None There are many warnings displayed during start up and it is easy to miss valid error messages. PROBLEM CONCLUSION: A new JVM property was created to control the messages displayed during server start up based on message type. The new property is: com.ibm.ws.webservices.startup.wsdl.suppressMessages This property can be set to one of the following case-sensitive values: NONE INFO WARNING ERROR ALL NONE - no messages will be suppressed INFO - only Info type messages will be suppressed WARNING - Warning and Info type messages will be suppressed ERROR - All messages will be suppressed ALL - All messages will be suppressed This fix is currently targeted for fix pack 6.1.0.15. 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 __ 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 __ 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 PKxxxxx.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 (PKxxxxx.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 (PKxxxxx.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: A custom JVM property must be set in order to take advantage of this fix - com.ibm.ws.webservices.startup.wsdl.suppressMessages 1. Set a custom JVM system property (com.ibm.ws.webservices.startup.wsdl.suppressMessages) in the AdminConsole. Navigate to Servers -> Application servers -> -> Java and Process Management -> Process Definition -> Java Virtual Machine -> Custom Properties Select "New" Enter the "Name" of the property Enter the "Value" of the property Enter the "Description" of the property Select "Apply" or "OK" Click on "Save" 2. Restart the server Valid values for the property are: NONE - does not suppress any messages (current behavior) INFO - only suppresses INFO messages WARNING - suppresses WARNING and INFO messages ERROR - suppresses ERROR, WARNING, and INFO messages ALL - suppresses all messages