Fix (APAR):  JR25220

Status:  Fix

Release:  6.0.1.3,6.0.1.2

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

Supersedes Fixes:  JR24505

CMVC Defect:  xxxxxx

Byte size of APAR:  50052

Date: 2006-12-12

Abstract:  When User Fault is thrown, it is caught as a remote exception at the client end.

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

ERROR DESCRIPTION:                                              
When User Fault is thrown, it is caught as a remote exception at
the client end.                                                 
                                                                
It appeaars that when invoked from BPEL, the user exception data
object is created as usual by instantiating the DataObject, but 
the SCA runtime loses the QName information in the process of   
serialization.This information is essential in order to be able 
to get the correct type at the target. Also, there needs to be a
global element in the WSDL schema definition that will refer to 
the user defined complex type for the exception.                
                                                                
this is a RemoteException                                       
                                                                
WebServicesFault                                                
 faultCode: {http://TestEx}SimpleException                      
 faultString: this should be a SimpleException                  
 faultActor: null                                               
 faultDetail:                                                   
 SimpleException: <message>this should be a                     
 SimpleException</message>                                      
                                                                
this should be a SimpleException                                
 at                                                             
com.ibm.ws.webservices.engine.WebServicesFault.makeUserFault(Web
Services                                                        
Fault.java:218)                                                 
 at                                                             
com.ibm.ws.webservices.engine.xmlsoap.builders.WebServicesFaultP
rocessor                                                        
.createFault(WebServicesFaultProcessor.java:407)                
 at                                                             
com.ibm.ws.webservices.engine.xmlsoap.SOAPFault.getFault(SOAPFau
lt.java:                                                        
486)                                                            
 at                                                             
com.ibm.ws.webservices.engine.SOAPPart.getFault(SOAPPart.java:10
90)                                                             
 at                                                             
com.ibm.ws.webservices.engine.SOAPPart.getFault(SOAPPart.java:74
7)                                                              
 at                                                             

LOCAL FIX:                                                      
NA                                                              

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x users who
export a BPEL process as a web service.

PROBLEM DESCRIPTION:
When User Fault is thrown, it is
caught as a remote exception at
the client end.

RECOMMENDATION:
None

The issue here is that a BPEL process exports itself as a
webservice. The client invoking this webservice is unable to
receive the expected Business Exception. Instead, it sees a
Remote Exception. SCA runtime not correctly serializing the
QName.

PROBLEM CONCLUSION:                                             
By using this IFIX we can see the Application specific Fault.   
This IFIX has a prereq -JR24007. While installation we have to  
first install JR24007 followed by JR25220. This IFIX superceeds 
JR24505.                                                        


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: