Fix (APAR): PK46313 Status: Fix Release: 6.0.2 Operating System: AIX,HP-UX,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: Byte size of APAR: 8829 Date: 2007-06-11 Abstract: The Health controller attempts to invoke ORB operations after it has shut down. Description/symptom of problem: PK46313 resolves the following problem: ERROR DESCRIPTION: We found "org.omg.CORBA.BAD_INV_ORDER: ORB has been shut down" exception on nodeagent trace log preceding the credential error. . It appears that nodeagent fails to create initial context token because ORB has already been shut down. And as a result the sendNotification operation of HAManagedItems MBean on XD component fails. When nodeagent receives stop signal from command line or from admin console, nodeagent process goes into stop operation. . You can see in the trace file that HAManagedItem MBean could not send notification to dmgr due to the failure of initialization of security component because ORB component has already been shut down. . "org.omg.CORBA.BAD_INV_ORDER: ORB has been shut down" error itself is logged at the timing both stop. - com.ibm.ws.runtime.component.TPVServiceImpl - com.ibm.ws.xd.hamitem.HAMItemManagerComponentImpl Not only at the timing HAMItemManagerComponentImpl, stops. However, TPVServiceImpl doesn't send notification to dmgr when it is shutting down so no exception is logged in dmgr log file. On the other hand, HAMItemManagerComponentImpl sends notification to dmgr (execute "sendNotification" method) when it is shutting down so ADMN0022E will be logged in nodeagent trace file. And SECJ0306E exception in dmgr SystemOut.log) SOAPConnector < handleAdminFault Exit javax.management.JMRuntimeException: ADMN0022E: Access is denied for the sendNotification operation on HAManagedItems MBean because of insufficient or empty credentials. LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Extended Deployment version 6.0.2 using Health policies. PROBLEM DESCRIPTION: The Health controller attempts to invoke ORB operations after it has shut down. RECOMMENDATION: None When the nodeagent running the Health Controller is brought down, the health controller sends out a JMX notification announcing its departure to all the other servers that are up and running. If the RMI connector is used for JMX messaging it relies on the ORB being up and running for its messaging capabilities. The shutdown of the health controller happens after that of the ORB and hence the health controllers attempt to send out a JMX notification over the ORB meets with an exception since the ORB has already been shutdown. PROBLEM CONCLUSION: This APAR fixes the Health Controller so that it announces its departure earlier in the server shutdown path before the ORB has been shutdown. This fix will be made available as part of WebSphere Extended Deployment 6.0.2 fix pack 1. Directions to apply fix: Install Fix to: NOTE: Developers - Place and X next to the proper installation method and remove this note _x_ 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. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack. DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Fix Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files. Customers must 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. 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). The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes 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. NOTE: 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: