Fix (APAR):  JR25730

Status:  Fix

Release:  6.0.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  23331

Date: 2007-02-11

Abstract:  A business process gets null input para meter value when it is invoked with asy nc mode and get error:

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

ERROR DESCRIPTION:                                              
When testing a business process that is using Data Objects      
from the Acord schema, the business process as a microflow      
(short-running process).  However when the is changed to a      
long-lived business process, the input data is received         
as a null object.                                               
                                                                
The Data Object in this case is from the Acord schema with      
namespace:                                                      
http://www.ACORD.org/standards/PC_Surety/ACORD1.8.0/xml/        
                                                                
                                                                
This error is due to a serialization problem which is required  
for a long-lived business process. The Data Object with this    
schema cannot be serialized.  Futher investigation shows that   
async or other serializations of this Data Object result in     
errors.                                                         

LOCAL FIX:                                                      
This root cause of this issue is with the way that the namespace
is processed during serialization.                              
http://www.ACORD.org/standards/PC_Surety/ACORD1.8.0/xml/        
                                                                
The internal mechanisms of the product to serialize this        
namespace result in a conflict between the last segment of the  
namespace, "xml", and the reserved "xml" namespace.             
                                                                
The workaround solution is to not have "xml" as the last part of
the namespace. For example:                                     
http://www.ACORD.org/standards/PC_Surety/ACORD1.8.0/acc/        

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2.x users.

PROBLEM DESCRIPTION:
A business process gets null input para
meter value when it is invoked with asy
nc mode and get error:

RECOMMENDATION:
None

If the xsd schema's name space ends with word 'xml' and a
message is created from the schema. When a client calls a SCA
component with async mode, the SCA component will deserialize
the async message. If the message is created from a xsd schema
that name space ends with word 'xml', it will throw the
following exception.

CNTR0020E: EJB threw an unexpected (non-declared) exception
during invocation of method "bpc_onMessage" on bean
"BeanId(raymodApp#raymodEJB.jar#component.Component1, null)".

Exception data: javax.jms.MessageFormatException:
CWSIA0121E: An exception occurred while serializing the object:
java.io.NotSerializableException: org.eclipse.emf.ecore.xml.
namespace.impl.XMLNamespaceFactoryImpl.java.io.
NotSerializableException: org.eclipse.emf.ecore.xml.namespace.
impl.XMLNamespaceFactoryImpl


PROBLEM CONCLUSION:                                             
The business process will get right input data when use the     
async invocation.                                               


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: