Fix (APAR):  JR25067

Status:  Fix

Release:  6.0.1.3

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

Supersedes Fixes:  

CMVC Defect:  JR25067

Byte size of APAR:  46640

Date: 2007-01-12

Abstract:  Business Object disappears after WPS picks it up from JMS queue. Turning up SCA trace shows, BasicIndexOutOfBoundsException thrown.

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

ERROR DESCRIPTION:                                              
Scenario: 1 schema, same namespace                              
(/OmsCommonLibrary/ICS_WPS_Lightspeed_R3-v1.1.xsd)              
Two complex types, one named order, and another named           
returnStatus both have private types defined as transactionInfo.
Although the BOXMLSerializer is able to writeDataObject(bo, uri,
name, System.out) without problems, the                         
com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl is not      
working properly (or the right definition is not being loaded   
properly).                                                      
                                                                
 <xs:complexType name="order">                                  
  <xs:annotation>                                               
   <xs:documentation>Service Order Sent from OMS to             
SDP</xs:documentation>                                          
  </xs:annotation>                                              
   <xs:sequence>                                                
<!-- ************************************* transactionInfo      
************************************* -->                       
    <xs:element name="transactionInfo">                         
     <xs:complexType>                                           
      <xs:sequence>                                             
       <xs:element name="interfaceName">                        
        <xs:simpleType>                                         
         <xs:restriction base="xs:string">                      
          <xs:minLength value="1"/>                             
          <xs:whiteSpace value="preserve"/>                     
          <xs:maxLength value="50"/>                            
         </xs:restriction>                                      
        </xs:simpleType>                                        
       </xs:element>                                            
       <xs:element name="correlationId">                        
        <xs:simpleType>                                         
         <xs:restriction base="xs:string">                      
          <xs:minLength value="1"/>                             
          <xs:maxLength value="19"/>                            
         </xs:restriction>                                      
        </xs:simpleType>                                        
       </xs:element>                                            
       <xs:element name="logicalServerName">                    
        <xs:simpleType>                                         
         <xs:restriction base="xs:string">                      
          <xs:minLength value="1"/>                             
          <xs:maxLength value="20"/>                            
         </xs:restriction>                                      
        </xs:simpleType>                                        
       </xs:element>                                            
       <xs:element name="transactionDateTimeStamp"              
type="xs:dateTime"/>                                            
       <xs:element name="versionNumber" minOccurs="0">          
        <xs:simpleType>                                         
         <xs:restriction base="xs:string">                      
          <xs:minLength value="1"/>                             
          <xs:maxLength value="10"/>                            
         </xs:restriction>                                      
        </xs:simpleType>                                        
       </xs:element>                                            
      </xs:sequence>                                            
     </xs:complexType>                                          
    </xs:element>                                               
[more xml omitted for clarity]                                  
                                                                
                                                                
  <xs:complexType name="returnStatus">                          
  <xs:annotation>                                               
   <xs:documentation>Service Order Status Sent from SDP to      
OMS</xs:documentation>                                          
  </xs:annotation>                                              
   <xs:sequence>                                                

LOCAL FIX:                                                      
<!-- workaround: renamed transactionInfo to                     
transactionInfoReturnLT -->                                     
    <xs:element name="transactionInfoReturnLT">                 
     <xs:complexType>                                           
      <xs:sequence>                                             
       <xs:element name="interfaceName">                        
        <xs:simpleType>                                         
         <xs:restriction base="xs:string">                      
          <xs:minLength value="1"/>                             
          <xs:maxLength value="50"/>                            
         </xs:restriction>                                      
        </xs:simpleType>                                        
       </xs:element>                                            
       <xs:element name="correlationId">                        
        <xs:simpleType>                                         
         <xs:restriction base="xs:string">                      
          <xs:maxLength value="19"/>                            
          <xs:minLength value="1"/>                             
         </xs:restriction>                                      
        </xs:simpleType>                                        
       </xs:element>                                            
       <xs:element name="logicalServerName">                    
        <xs:simpleType>                                         
         <xs:restriction base="xs:string">                      
          <xs:maxLength value="20"/>                            
          <xs:minLength value="1"/>                             
         </xs:restriction>                                      
        </xs:simpleType>                                        
       </xs:element>                                            
      </xs:sequence>                                            
     </xs:complexType>                                          
    </xs:element>                                               
[more xml omitted for clarity]                                  
                                                                
This scenario causes problems during a oneway async call.       

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.1.x users
having XML schemas with parent
element name same as child element of
another complex type element..

PROBLEM DESCRIPTION:
Business Object disappears after WPS
picks it up from JMS queue. Turning
up SCA trace shows,
BasicIndexOutOfBoundsException thrown.

RECOMMENDATION:
None

Two complex types, one named order, and another named
returnStatus both have private types defined as
transactionInfo.  Although the BOXMLSerializer is able to
writeDataObject(bo, uri, name, System.out) without problems,
the com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl is not
working properly (or the right definition is not being loaded
properly).

PROBLEM CONCLUSION:                                             
BOXMLSerializer (part of BO CoreFrameWork) was getting          
confused between the two definitions of "transactionInfo"       
private types declared. This is was the limitation of EMF,      
that BO uses for serialation and deserialization. BO            
CoreFramework code was modified to take care of this            
limitation and avoid confusion in resolution of duplicate       
private types.                                                  


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 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 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) 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: