Fix (APAR):  JR31349

Status:  Fix

Release:  6.2.0

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  9944

Date: 2008-12-12

Abstract:  After migration from WebSphere Enterprise Service Bus 6.1.x to WebSphere Enterprise Service Bus 6.2.0.0, the runtime exceptions raised from Service Component Architecture (SCA) asy

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

ERROR DESCRIPTION:?                                             
During ESB Migration from 61 to 62, the old SCA application     
queue's excpetion destination is updated with a wrong queue     
name.                                                           

LOCAL FIX:?                                                     

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server V6.2.0 users.

PROBLEM DESCRIPTION:
After migration from WebSphere
Enterprise Service Bus 6.1.x to
WebSphere Enterprise Service Bus
6.2.0.0, the runtime exceptions
raised from Service Component
Architecture (SCA) asynchronous
invocation by old applications can
not be handled as failed events.

RECOMMENDATION:
None

The problem can be reproduced after migration from WebSphere
Enterprise Service Bus 6.1.x to WebSphere Enterprise Service
Bus 6.2.0.0. After migration, the activation specifications
name of Recovery service and the "Exception destination"
property of the Service Component Architecture (SCA)
destinations are set incorrectly. Hence, the error message can
not be routed to Failed Event destination and can not be
handled by Recovery service.

PROBLEM CONCLUSION:?                                            
Fixing the problem, in ESBRecoveryUpgrade.py file, modify the   
wrong activation specification name and exception destination   
to correct value.                                               
                                                                
Applying this interim fix will resolve the issue.               


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: