Fix (APAR):  JR31940

Status:  Fix

Release:  6.1.2.2,6.1.2.1,6.1.2

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

Supersedes Fixes:  

CMVC Defect:  JR31940

Byte size of APAR:  62981

Date: 2009-02-19

Abstract:  When deploying a service component architecture (SCA) module that contains Event Sequencing qualifiers to a deployment target that references remote Messaging Engines, the creation

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

ERROR DESCRIPTION:                                             
Component level Queue destinations are not created for modules  
with Event sequencing. As a result During start up of           
Cluster/server The following exception is thrown                
********               
1/30/09 13:32:36:078 PST  0000000a  WSVR0001I:
Applicaton open for e-business           
1/30/09 13:32:41:953 PST  00000034              
com.ibm.wbiserver.sequencing.service.messaging.EsMeConnectionService                                                            
start() Failed to connect to the ME on the SCA system bus that  
hosts esDestination=sca/name/component/name
Reason: com.ibm.websphere.sib.exception.SIResourceException:    
CWSIT0086E:                                                     
Bus SCA.SYSTEM.Cell.Bus not found 
                                         
*****************                                               

LOCAL FIX:                                                     
an iFix is available                                            

PROBLEM SUMMARY:

USERS AFFECTED:
WebSphere Process Server v6.1.0.x and
v6.1.2.x users.

PROBLEM DESCRIPTION:
When deploying a service component
architecture (SCA) module that
contains Event Sequencing qualifiers
to a deployment target that
references remote Messaging Engines,
the creation of system component
queues fails to resolve and create
the queues.

RECOMMENDATION:
None

Event Sequencing system component queue creation fails.

PROBLEM CONCLUSION:                                            
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.