Fix (APAR):  JR30178

Status:  Fix

Release:  6.0.2.4

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

Supersedes Fixes:  

CMVC Defect:  JR30178

Byte size of APAR:  51508

Date: 2008-10-22

Abstract:  Customers, in an Network deployment environment, would like to see messages stuck, if any,in BPE Hold and rentention queues through Admin Console. These customers will see incorrec

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

ERROR DESCRIPTION:?                                             
Messages are processed to retention and hold queues.  It is not 
possible to reply these, because the messages are not visible in
the admin console.                                              
                                                                
                                                                
This is currently seen on WPS 6.0.2.3.                          
                                                                
Has been accepted as a defect by WPS admin console development. 

LOCAL FIX:?                                                     
none.                                                           

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server 6.0.2.x customers,
who have Network Deployment environment,
operating in a Multi Application Cluster
environment.

PROBLEM DESCRIPTION:
Customers, in an Network deployment
environment, would like to see
messages stuck, if any,in BPE Hold and
rentention queues through Admin
Console. These customers will see
incorrect status for the messages in
BPE Hold and retention queues. More
specifically, when status of those
queues are checked in the admin
console for an application cluster,
which is partially or totally down.

RECOMMENDATION:
None

Code to handle network deployment envionment was missing.
As a result of which, it was sending incorrect parameters to
the MBean initialization. This results in incorrect selection
of cluster.

PROBLEM CONCLUSION:?                                            
Code has been added to address network deployment and           
right parameters are now being sent to MBean initialization.    
Applying the interim fix will resolve the problem.              


Directions to apply fix:  
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 Process Server.

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 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.

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

3) Restart WebSphere Process Server.

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: