Fix (APAR): PK17866 Status: Fix Release: 5.1.1.8 Operating System: AIX,HP-UX,Linux,Linux Red Hat - pSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: PK17866 Byte size of APAR: 959838 Date: 2006-02-13 Abstract: After application of 5.1.1.8, an MDB Message Listener will fail to start if it is defined with a WebSphere MQ Queue Connection Factory which has an empty Queue Manager definition Description/symptom of problem: PK17866 resolves the following problem: ERROR DESCRIPTION: WebSphere Application Server cumulative fix 5.1.1.8 contains apar PQ97829. This apar changed the behavior for the queue manager property in queue connection factories to allow them to use websphere variables. With PQ97829 the queue manager field was not expected to be blank so therefore a NullPointerException is thrown when the queue connection factory tries to bind into the namespace. The queue manager field is not listed as a required field and there are legitimate cases where it is left blank, so this behavior needs to be changed so that an empty queue manager field is allowed. An example of the error: [1/11/06 13:35:56:892 CST] 70520252 ResourceMgrIm E WSVR0017E: Error encountered binding the J2EE resource, DefaultQCF, as jms/DefaultQCF from file:/opt/WebSphere/AppServer/config/cells/mycell/resources.xml java.lang.NullPointerException at com.ibm.ws.runtime.component.binder.MQQueueConnectionFactoryBind er.getBindingObject(MQQueueConnectionFactoryBinder.java:116) at com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImp l.java:287) at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProv ider(ResourceMgrImpl.java:812) ... LOCAL FIX: The error won't occur if the queue manager field has a value. PROBLEM SUMMARY USERS AFFECTED: This problem affects customers who use the Java Message Service (JMS) functionality provided with WebSphere Application Server Version 5. PROBLEM DESCRIPTION: After application of 5.1.1.8, an MDB Message Listener will fail to start if it is defined with a WebSphere MQ Queue Connection Factory which has an empty Queue Manager definition RECOMMENDATION: None PQ97829 extended the handling of the Queue Manager field to handle variable substitution, but incorrectly fails in the case of the Queue Manager field being undefined. PROBLEM CONCLUSION: The MDB Message Listener code has been modified to correctly handle an empty queue manager definition from a WebSphere MQ queue connection factory. The fix for this APAR is currently targeted for inclusion in Cumulative Fix 10 for WebSphere Application Server Version 5.1.1. Please refer to the Recommended Updates page for delivery dates: 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: 5.0 5.1 ___ _X_ Application Server (Express or BASE) Install Fix to: Method: X_ Application Server Nodes NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack. The Update 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. 1) Copy PK17866_5118.jar 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 (PK17866_5118.jar 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. * 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 (PK17866_5118.jar). 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: