Fix (APAR):  PK15976

Status:  Fix

Release:  6.0.2.3

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

Supersedes Fixes:  

CMVC Defect:  325186

Byte size of APAR:  28085

Date: 2005-12-15

Abstract:  When messages are sent from WebSphere MQ (MQ) to WebSphere using the default messaging provider and the MQLink, their header properties may be incorrectly returned in the results f

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

ERROR DESCRIPTION:                                              
When messages are sent from WebSphere MQ (MQ) to WebSphere      
using the default provider and the MQLink, their header         
properties may be incorrectly displayed in the results for      
"getPropertyNameSet()".                                         
                                                                
Also if messages are sent from MQ to WebSphere default          
messaging and the same messages are forwarded back to MQ        
again, header properties may be lost. This does not affect      
messages created through WebSphere default messaging.           

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
Users of WebSphere messaging with the MQ
Link

PROBLEM DESCRIPTION:
When messages are sent from WebSphere
MQ (MQ) to WebSphere using the default
messaging provider and the MQLink,
their header properties may be
incorrectly returned in the results
for "getPropertyNameSet()".
propertyExists() may return true
incorrectly for some properties which
do not exist.

Also if messages are sent from MQ to
WebSphere default
messaging and the same messages are
forwarded back to MQ
again, header properties may be lost.
This does not affect
messages created using WebSphere
default messaging as a JMS provider.

RECOMMENDATION:
None

getPropertyNameset() and propertyExists() have been changed to
reflect the header properties correctly.

PROBLEM CONCLUSION:                                             
This fix solves the problem.                                    

Directions to apply fix:  Fix applies to Editions:
Release 6.0
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)

Install Fix to:
Method:
__ Application Server 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 PK15976.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 (PK15976.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 (PK15976.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: