Fix (APAR): PK28310 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,z/OS Supersedes Fixes: CMVC Defect: PK28310 Byte size of APAR: 12206 Date: 2006-07-24 Abstract: An issue within an MDB application was hit whereby it received the following exception repeatedly after a failure occures initializing the MDB: IllegalStateException: MessageEndpo Description/symptom of problem: PK28310 resolves the following problem: ERROR DESCRIPTION: An issue within an MDB application was hit whereby it received the following exception repeatedly after a failure occures initializing the MDB: IllegalStateException: MessageEndpoint proxy used after MessageEndpoint.release was called. Internal state = 1 This is caused when an exception is thrown in a MessageDriven beans ejbCreate() method, causing WebSphere to fail to create a message endpoint and the SystemOut.log is filled with error messages in an infinite loop. After a while the node stops responding. LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: All WebSphere Application Server version 6.0 users who use MDBs that happen to throw an exception during the MDBs ejbCreate method. PROBLEM DESCRIPTION: An issue within an MDB application was hit whereby it received the following exception repeatedly after a failure occures initializing the MDB: IllegalStateException: MessageEndpoint proxy used after MessageEndpoint.release was called. Internal state = 1 RECOMMENDATION: None The IllegalStateException is caused when an exception is thrown in a MessageDriven beans ejbCreate() method, causing WebSphere to fail to create a message endpoint and the SystemOut.log is filled with error messages in an infinite loop. After a while the node stops responding. When the MDB's ejbCreate throws an exception, the exception is not handled appropriately by WebSphere thus leaving the MDB in an improper state. When this MDB is accessed subsequent times, it is found to be in an improper state and the IllegalStateException and message shown above will be reported to the user. PROBLEM CONCLUSION: After applying this fix, the appropriate code will be executed to properly handle the case where an MDB's ejbCreate method throws an exception. The MDB will be put into the correct state in this scenario thus leaving it in a proper state for subsequent requests. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.11. 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) _X_ Network Deployment (ND) _X_ WebSphere Business Integration Server Foundation (WBISF) _X_ Edge Components _X_ Developer _X_ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes _X_ 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.9-WS-WAS-IFPK28310.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.9-WS-WAS-IFPK28310.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.9-WS-WAS-IFPK28310.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: