Fix (APAR):  JR25397

Status:  Fix

Release:  6.0.1.4

Operating System:  Windows

Supersedes Fixes:  

CMVC Defect:  JR25397

Byte size of APAR:  86991

Date: 2007-02-16

Abstract:  WPS throws a assertion violation exception for a bpel process.  After restarting the server and the problem doesn't exist.

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

ERROR DESCRIPTION:                                              
Customer has a process that included human tasks.  Sometimes    
they receive an assertion violation when completing the human   
task.  This is seemingly the result of the isInstance method    
returning false                                                 
                                                                
Problem is not reproducible in house and happens inconsistently 
at customer site.                                               
                                                                
Customer is on 6.0.1.3 in production, so fix should be on that  
version                                                         

LOCAL FIX:                                                      
none.  requires restart of server                               

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x users.

PROBLEM DESCRIPTION:
WPS throws a assertion violation
exception for a bpel process.  After
restarting the server and the problem
doesn't exist.


RECOMMENDATION:
None

WPS throws a assertion violation exception for bpel process.
After restarting the server and the problem doesn't exist.
This problem occurs when an inline task is completed.

The assertion occurs because the type-check of the message
fails in the BPEL process while calling Type.isInstance()
which returns false where it should be true, as 2 different
API's are used to complete the inline task FlowManager API
and Task Manager API and CSD cache gets does'nt load the
appropriate BO objects from the class loader as the cache is
corrupt.

PROBLEM CONCLUSION:                                             
BO class loader cache is cleaned and appropriate BO are         
loaded.                                                         


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: