Fix (APAR): PM31735 Status: Fix Release: 6.1.1.2,6.1.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: PK99664;PM04611;PM05220;PM06349;PM07037;PM08969;PM11582;PM11623;PM12939;PM18326;PM22866;PM25095;PM30114 CMVC Defect: PM31735 Byte size of APAR: 490391 Date: 2011-03-02 Abstract: The plugin-cfg.xml file does not contain routes for all modules and the ODR returns 404 error codes for the missing modules. Description/symptom of problem: PM31735 resolves the following problem: ERROR DESCRIPTION: After deploying an application if the resRefBindings's bindingResourceRef is null, the web modules of the application are not be listed in the ODR target.xml file or the ODR-generated plugin-cfg.xml file. The following exception is displayed: Stack Dump = java.lang.NullPointerException at com.ibm.ws.odc.xd.XDTreeBuilder.getResourceRefBindings (XDTreeBuilder.java:5023) at com.ibm.ws.odc.xd.XDTreeBuilder.processWebJMSBindings (XDTreeBuilder.java:4713) at com.ibm.ws.odc.xd.XDTreeBuilder.processWebModule(XDTreeBuilder. java:4440) at com.ibm.ws.odc.nd.cell.TreeBuilder.readApplication(TreeBuilder. java:1984) at com.ibm.ws.odc.nd.cell.TreeBuilder.readApplication(TreeBuilder. java:1832) at com.ibm.ws.odc.xd.XDTreeBuilder.readApplication(XDTreeBuilder. java:757) at com.ibm.ws.odc.nd.cell.TreeBuilder.doConfigChangePostProcessing (TreeBuilder.java:3256) at com.ibm.ws.odc.xd.XDTreeBuilder.doConfigChangePostProcessing(XDT (XDTreeBuildr.java:587) at com.ibm.ws.odc.nd.cell.TreeBuilder.handleConfigChange (TreeBuilder.java:3103) at com.ibm.ws.odc.nd.cell.TreeBuilder.configChanged(TreeBuilder. java:3042) at com.ibm.ws.odc.nd.cell.TreeBuilder$LocalEventListener. ConfigChanged(TreeBuilder.java:5184) LOCAL FIX: Until the fix is applied resolve the issue where the resRefBindings's bindingResourceRef is set to null. THis needs to be set to a non null value. PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Virtual Enterprise PROBLEM DESCRIPTION: The plugin-cfg.xml file does not contain routes for all modules and the ODR returns 404 error codes for the missing modules. RECOMMENDATION: None A null pointer exception (NPE) occurs if an invalid resource reference is encountered during start-up when the on demand configuration (ODC) component is incorporating application data into the data structure. The NPE causes the loss of all module data for the application with the invalid resource reference within the ODC data structure, which results in the on demand router returning 404 error codes for requests targeted for those modules and the absence of these modules in the ODC-generated plugin-cfg.xml file. PROBLEM CONCLUSION: ODC was updated to correctly handle invalid resource references, preventing the loss of the application module data within the data structure. This fix will be included in the next available fix pack for WebSphere Virtual Enterprise. Directions to apply fix: Install Fix to: __ 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. 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.1.0.17 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 6.1.1.0-WS-WXD-IFPM31735.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.1.1.0-WS-WXD-IFPM31735.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 (6.1.1.0-WS-WXD-IFPM31735.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: