Fix (APAR):  JR26957

Status:  Fix

Release:  6.0.1.6

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  29112

Date: 2007-07-18

Abstract:  WebSphere Process Server throws the following exception "java.io.NotSerializableException: com.ibm.wsspi.core.extension.model. symbol.classifier.FactoryAggregate".

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

ERROR DESCRIPTION:                                              
Emulate customer's scenario and make a simple scenario to test  
for                                                             
ClassNotFoundException. And debug WPS code.                     
The EClass name "AirNZ_UpgradeReBookRQ_._1_._type" should be a  
rename of                                                       
same xml name with  "AirNZ_UpgradeReBookRQ_._type".             
It seems that there are two EClass generated in coreFramework   
for                                                             
anonymous complex type defined in element                       
"AirNZ_UpgradeReBookRQ" in                                      
AirNZ_UpgradeReBookRQ.xsd. But there should only one EClass with
name                                                            
"AirNZ_UpgradeReBookRQ_._type".                                 
From my debug for a simple scenario, coreFramework builds       
duplicated                                                      
EClass for one anonymous complex type.                          

LOCAL FIX:                                                      
No                                                              

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server and
WebSphere Enterprise Service Bus
6.0.1.x and 6.0.2.x users.

PROBLEM DESCRIPTION:
WebSphere Process Server throws the
following exception
"java.io.NotSerializableException:
com.ibm.wsspi.core.extension.model.
symbol.classifier.FactoryAggregate".

RECOMMENDATION:
None

The class of com.ibm.wsspi.core.extension.
model.symbol.classifier.FactoryAggregate
does not implement Serializable interface. So FactoryAggregate
can not be serialized.
BO framework builds duplciated EClasses for same anonymous
complex type.
It causes WPS conflicts in some situations and then causes an
instance of FactoryAggregate into BPE message.
When BPE serialzes the message, it will try to serialze the
instance of FactoryAggregate and it will get
NotSerializableException.

PROBLEM CONCLUSION:                                             
With the iFix, BO framework will build one EClass for each      
anonymous complex type. The customer's issuce can be resolved   
by 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: