Fix (APAR): PK47327 Status: Fix Release: 6.0.2.21,6.0.2.19 Operating System: AIX,HP-UX,Linux,Linux pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: PK47327 Byte size of APAR: 36584 Date: 2007-08-21 Abstract: When you try to import a profile with multiple servers in it you see the following exception in Systemout.log SECJ0007E: Error during security initialization. The exception is com Description/symptom of problem: PK47327 resolves the following problem: ERROR DESCRIPTION: A mismatch in server.xml and security.xml causes the errors below to be displayed in the systemout upon startup. 000000a distSecurityC E SECJ0007E: Error during security initialization. The exception is com.ibm.ws.exception.WsRuntimeException: java.lang.NullPointerException at com.ibm.ws.management.component.JMXConnectors.stateChanged(JMXCo nnectors .java:1524) at com.ibm.ws.security.core.distSecurityComponentImpl.fireEvent(dis tSecurit yComponentImpl.java:1651) at com.ibm.ws.security.core.distSecurityComponentImpl.fireStartedEv ent(dist SecurityComponentImpl.java:1607) at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity (distSec urityComponentImpl.java:299) at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(Sec urityCom ponentImpl.java:101) at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(Serve rSecurit yComponentImpl.java:280) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(Conta inerImpl .java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.j ava:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(Applica tionServ erImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(Conta inerImpl .java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.j ava:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:42 7) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl .java:18 7) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.jav a:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.jav a:58) at LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: Users of IBM Websphere Application Server versions 6.0.2 and 6.1 PROBLEM DESCRIPTION: When you try to import a profile with multiple servers in it you see the following exception in Systemout.log SECJ0007E: Error during security initialization. The exception is com.ibm.ws.exception.WsRuntimeException :java.lang.NullPointerException RECOMMENDATION: None While trying to import a profile with multiple servers there is a mismatch in the server.xml and security.xml which causes the following exceptions in the SystemOut.log upon startup. 000000a distSecurityC E SECJ0007E: Error during security initialization. The exception is com.ibm.ws.exception. WsRuntimeException:java.lang.NullPointerException at com.ibm.ws.management.component.JMXConnectors.stateChanged (JMXConnectors.java:1524) at com.ibm.ws.security.core.distSecurityComponentImpl. fireEvent(distSecurityComponentImpl.java:1651) .............. ............... The mismatch was due to a incorrect variable used in the algorithm to update the security.xml during import. PROBLEM CONCLUSION: The code has been modified to correct the problematic algorithm and thus preventing the problem while importing profile with multiple servers. This fix is targetted for fixpacks 6.0.2.23 and 6.1.0.13 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 _y_ Application Server (Express or BASE) _Y_ 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 _Y_ 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.6 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.21-WS-WAS-IFPK47327.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.21-WS-WAS-IFPK47327.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: