Fix (APAR):  PK67271

Status:  Fix

Release:  6.0.2.27,6.0.2.25,6.0.2.23,6.0.2.21,6.0.2.19,6.0.2.17,6.0.2.15

Operating System:  AIX,HP-UX,Linux,Linux pSeries,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  524963

Byte size of APAR:  47478

Date: 2008-06-16

Abstract:  NoClassDefFoundError during startup of application server when binding WebSphere MQ JMS resources into the JNDI namespace. The WebSphere MQ JMS resources cannot be used.

Description/symptom of problem:  
PK67271 resolves the following problem:

ERROR DESCRIPTION:                                              
A java.lang.NoClassDefFoundError is seen during server startup  
when WebSphere MQ V7 JMS resources are been bound into JNDI.    
This error will cause these resources to not be available from  
the JNDI namespace. The class not found is:                     
  com.ibm.mq.jms.services.ConfigEnvironment                     

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
 Users of WebSphere Application Server V6.0
using WebSphere MQ V7 as a messaging
provider, with an external WebSphere MQ V7
client or server installation installed and
pointed to by the MQ_INSTALL_ROOT
environment variable.

PROBLEM DESCRIPTION:
NoClassDefFoundError during startup
of application server when binding
WebSphere MQ JMS resources into the
JNDI namespace. The WebSphere MQ JMS
resources cannot be used.

RECOMMENDATION:
None

A class referenced by WebSphere Application Server V6.0 in the
WebSphere MQ JMS client is not available in the
WebSphere MQ V7 JMS client.

This issue only affects users with an MQ_INSTALL_ROOT
environment variable set to point at an external WebSphere
MQ V7 client or server installation.

PROBLEM CONCLUSION:                                             
This APAR solves the problem and allows the WebSphere MQ JMS    
resources to be bound into the WebSphere Application Server     
JNDI namespace.                                                 
                                                                
The fix for this APAR is currently targeted for inclusion in    
fixpack 6.0.2.29.  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:  Fix applies to Editions:
Release 6.0.2.15 - 6.0.2.27
__ Application Server (Express or BASE)
__ Network Deployment (ND)

Install Fix to:
Method:
__ Both Application Server Nodes and Deployment Manager Nodes

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 <was_root>/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.27-WS-WAS-IFPK67271.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.27-WS-WAS-IFPK67271.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.27-WS-WAS-IFPK67271.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: