Fix (APAR):  JR30236

Status:  Fix

Release:  6.1.0.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  8865

Date: 2008-09-18

Abstract:  Customers using multiple threaded clients, which invoke Service Component Architecture services based on asynchronous bindings simultaenoulsy. This error initially manifests with n

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

ERROR DESCRIPTION:?                                             
The customer has a JMS Export and when the customer's           
client sends a message to the JMS Export, on the first and only 
on the first message, they get this exception:                  
                                                                
[7/15/08 18:00:29:364 CEST] 0000003d TraceBPE      3            
com.ibm.bpe.framework.sca.ServiceCallbackReplyContext.<init>(Ser
viceCall                                                        
backReplyContext.java:118)                                      
scaMessage->InteractionHeader->callbackProxy                    
== null                                                         
                                                                
java.lang.IllegalArgumentException:                             
scaMessage->InteractionHeader->callbackProxy == null            
 at                                                             
com.ibm.bpe.framework.sca.ServiceCallbackReplyContext.<init>(Ser
viceCall                                                        
backReplyContext.java:117)                                      
...                                                             
                                                                
but after the first message, things seem to work fine. BPC L3   
analyzed                                                        
this issue and says that from their side, everything seems fine 
and the                                                         
reason why they are getting this exception is that the SCA is   
passing                                                         
them a NULL argument in the callbackProxy.                      
The strange thing is that this exception is only occuring when  
the first                                                       
message is sent but is fine for the subsequent messages. The    
call is an                                                      
Asynchronous call.                                              

LOCAL FIX:?                                                     
N/A                                                             

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server 6.1.0.x customers
invoking various Service Component
Architecture asynchronous bindings, such
as JMS, MQ-JMS, Native MQ, across multiple
threads.

PROBLEM DESCRIPTION:
Customers using multiple threaded
clients, which invoke Service
Component Architecture services
based on asynchronous bindings
simultaenoulsy. This error initially
manifests with null pointer exception
and generation of FFDC's. Due to
this, Callback proxy is
incorrectly set to null.
When Downstream components receive a
message with null callback proxy
illegal Argument exception is thrown
and transaction is rolled back.

RECOMMENDATION:
None

The problem is due to lack of thread synchronization, during
creation of various message handlers.

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.

Additional Information: