Fix (APAR):  JR26018

Status:  Fix

Release:  6.0.1.5,6.0.1.4,6.0.1.3

Operating System:  AIX,HP-UX,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  JR26018

Byte size of APAR:  31424

Date: 2007-03-26

Abstract:  purge policy attribute changed after deploy PI to server.

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

ERROR DESCRIPTION:                                              
"Purge policy" property of JMS import is changed after          
deploying it to WPS server.                                     
In the JMS binding the property is set to "entirePool" at       
development time. When it is viewed at runtime the property     
value got changed to "FailingConnection Only".                  

LOCAL FIX:                                                      
N/A                                                             

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x users

PROBLEM DESCRIPTION:
purge policy attribute changed after
deploy PI to server.

RECOMMENDATION:
None

If there is JMS import binding in PI, there will be an
attribute purge policy with default value "entire pool", but
after deploy to server, the property change to "failed pool
only"

PROBLEM CONCLUSION:                                             
This was a defect for WebSphere Process Server, if all          
attributes use default value, when depolyed to the server, the  
attribute will be null. And then WebSphere Information          
Developer will desplay a random value. Now we set attribute     
when all values is default value.                               


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system.
Also download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed

1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server

Additional Information: