Fix (APAR): PK30272 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: PK30272 Byte size of APAR: 7250 Date: 2006-09-14 Abstract: When an ejb home object is used that is no longer valid, a HomeDisabledException is thrown. This is expected behavior, however, the exception is printed to the system logs which ma Description/symptom of problem: PK30272 resolves the following problem: ERROR DESCRIPTION: WebSphere Process Server users experience a HomeDisabledException when an application containing EJBs is uninstalled and then reinstalled. The problem occurs for applications which use the Business Process Choreographer. The exception does not cause functional loss. An exception similar to the following is logged to the SystemOut.log and the trace.log: [7/25/06 8:40:29:676 CST] 0000005c ExceptionUtil E CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "create". Exception data: com.ibm.ejs.container.CreateFailureException: ; nested exception is: com.ibm.ejs.container.HomeDisabledException: com.mycomp.myApp#com.mycomp.myEJB.jar#component.theBean at com.ibm.bpe.framework.sca.EJSStatelesscomponent_theBeanHome Bean_2ece450d.create_Local(EJSStatelesscomponent_theBeanHom eBean_2ece450d.java:33) at com.ibm.bpe.framework.sca.EJSLocalStatelesscomponent_theBean Home_2ece450d.create(EJSLocalStatelesscomponent_theBeanHom e_2ece450d.java:28) at com.ibm.bpe.framework.sca.ProcessImplementationHandler.lookupFac adeSessionBean(ProcessImplementationHandler.java:505) at com.ibm.bpe.framework.sca.ProcessImplementationHandler.handleAsy ncResponseCallbackMessage(ProcessImplementationHandler.java:348) LOCAL FIX: The exception does not cause functional loss and can be ignored. PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server version 6.0.2 and 6.1 users. PROBLEM DESCRIPTION: When an ejb home object is used that is no longer valid, a HomeDisabledException is thrown. This is expected behavior, however, the exception is printed to the system logs which may not be desired. RECOMMENDATION: None When a user uses a home object that is no longer a valid, a HomeDisabledException will be thrown and printed to the system logs. An example of where a home object may become invalid is as follows: a user looks up a home and caches the resultant home object. Next, the application that the home belongs to is stopped and restarted. The user with the cached home object now has a reference to a home that no longer exists. As such, when it uses the cached home object, a HomeDisabledException will occur. This exception is expected behavior, however, the HomeDiabledException will be printed to the system logs. This is not an error by any means, but some users may not want this exception printed to their system logs. PROBLEM CONCLUSION: With this fix, the HomeDisabledException will no longer be printed to the system logs. The HomeDisabledException will still be thrown in the scenarios that warrant it, however in those cases, this exception will not be printed to the system logs. 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 _X_ 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.11-WS-WAS-IFPK30272.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-IFPK30272.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-IFPK30272.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: