Fix (APAR):  JR25305

Status:  Fix

Release:  6.0.1.3

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  18893

Date: 2006-11-27

Abstract:  A Business State Machine can invoke another Service.  If an error occurs in this service, the Business State Machine may fail.  Future commands to the Business State Machine may re

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

ERROR DESCRIPTION:                                              
A Business State Machine can invoke another Service.  If an     
error occurs in this service, the Business State Machine may    
fail.                                                           
                                                                
Future commands to the Business State Machine may result in     
error:                                                          
                                                                
CWWBE0066E:                                                     
  A two-way Request for port type 'MyInterface' and             
operation                                                       
  'MyOperation' was received, but there is                      
currently                                                       
  a conflicting request for the same port type and operation    
being                                                           
  processed.                                                    
                                                                
                                                                
The underlying BPEL generated by the Business State Machine has 
incorrectly generated code for fault handling.                  
If BPE Tracing is turned on, the following message may be seen: 
                                                                
[11/8/06 18:12:54:590 CET] 00000064 TraceBPE      3             
com.ibm.bpe.engine.BpelActivityKindReply.doActivate(BpelActivity
KindRepl                                                        
y.java:165) CWWBE0068E: During process execution, activity      
'activity779'                                                   
tried to access an uninitialized part in variable               
'BSMFaultReturnMessage'.                                        
                                                                
                                                                
This variable is used during the handling of the fault within an
invoke.  Since this fails, the invoke never completes, and      
future operations to the Business State Machine will result in  
the "conflicting request" error above.                          

LOCAL FIX:                                                      
None.                                                           

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x users.

PROBLEM DESCRIPTION:
A Business State Machine can invoke
another Service.  If an error occurs
in this service, the Business State
Machine may fail.

Future commands to the Business State
Machine may result in error:

CWWBE0066E:
A two-way Request for port type
'MyInterface' and operation
'MyOperation' was received, but there
is currently a conflicting request for
the same port type and operation being
processed.

RECOMMENDATION:
None

The underlying BPEL generated by the Business State Machine has
incorrectly generated code for fault handling.
If BPE Tracing is turned on, the following message may be seen:

[11/8/06 18:12:54:590 CET] 00000064 TraceBPE      3
com.ibm.bpe.engine.BpelActivityKindReply.doActivate(BpelActivity

KindRepl
y.java:165) CWWBE0068E: During process execution, activity
'activity779'
tried to access an uninitialized part in variable
'BSMFaultReturnMessage'.


This variable is used during the handling of the fault within an

invoke.  Since this fails, the invoke never completes, and
future operations to the Business State Machine will result in
the "conflicting request" error above.

PROBLEM CONCLUSION:                                             
Problem has been fixed and is included in the next WBISF        
service pack.                                                   


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: