Fix (APAR):  JR25836

Status:  Fix

Release:  6.0.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  11873

Date: 2007-03-04

Abstract:  SCA serializer throws serviceIllegalArgumentException when using JMS import binding & MQ import binding to serialize the dataobject created by an anonymous complex type.

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

ERROR DESCRIPTION:                                              
Customer receives IllegalArgumentException:                     
{ShippingOrder_._type}ShippingOrder_._type is                   
not corresponding to a global element.                          
                                                                
Schema has anonymous complex types.                             
                                                                
This is occuring on 602                                         

LOCAL FIX:                                                      
edit schema                                                     

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2.x users

PROBLEM DESCRIPTION:
SCA serializer throws
serviceIllegalArgumentException when
using JMS import binding & MQ import
binding to serialize the dataobject
created by an anonymous complex type.


RECOMMENDATION:
None

For an anonymous complex type definition, WPS may build the
duplicated EClassifiers for the same anonymous complex type in
some special scenarios.
So it causes JMS import binding & MQ import binding to get
IllegalArgumentException during the serializing. In other
scenarios, WPS may show other errors caused by the duplicated
EClassifiers.

The exception is something like:
java.lang.IllegalArgumentException: {ShippingOrder_._type}
ShippingOrder_._type is not corresponding to a global element.

at com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl.
attachRootObject(XMLFileServiceImpl.java:430)

at com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl.save
(XMLFileServiceImpl.java:296)

at com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl.save
(XMLFileServiceImpl.java:367)

at com.ibm.wsspi.sca.sdo.XMLFileService$1.save
(XMLFileService.java:88)

at com.ibm.ws.sca.databinding.impl.DataBindingImplXML$1.run
(DataBindingImplXML.java:167)

at java.security.AccessController.doPrivileged1(Native Method)

at java.security.AccessController.doPrivileged
(AccessController.java(Compiled Code))

at com.ibm.ws.sca.databinding.impl.DataBindingImplXML.write
(DataBindingImplXML.java:164)

at com.ibm.ws.sca.databinding.impl.DataBindingImplXML.
getAsString(DataBindingImplXML.java:99)

PROBLEM CONCLUSION:                                             
The problem has been resolved by applying the iFix.             


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: