Fix (APAR):  JR26339

Status:  Fix

Release:  6.0.1.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  14131

Date: 2007-04-19

Abstract:  When a source sca component makes a async twoway call to a target sca component through an interface map and the target component returns a fault to the source component, there is 

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

ERROR DESCRIPTION:                                              
When a fault is passed back to the calling module from the      
called module, it seems to be expecting the Output business     
object rather than the Fault object, so we get a class cast     
exception.                                                      

LOCAL FIX:                                                      
No local fix                                                    

PROBLEM SUMMARY

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

PROBLEM DESCRIPTION:
When a source sca component makes a
async twoway call to a target sca
component through an interface map and
the target component returns a fault
to the source component, there is
ClassCastException happening when
returning the fault to the source
component.

RECOMMENDATION:
None

The source sca component and the target sca component can
exist in different SCA module and they are connected by import
and export. The source sca component and the target sca
component can also exist in the same SCA module.

The ClassCastException happening when returning the fault to
the source component.
java.lang.ClassCastException: com/ibm/websphere/sca/
ServiceBusinessException    incompatible with
org/eclipse/emf/ecore/EObject

at com.ibm.ws.sca.internal.mediation.handler.
InterfaceMediationHandler.mediateNonWrapper2Wrapper
(InterfaceMediationHandler.java:658)

at com.ibm.ws.sca.internal.mediation.handler.
InterfaceMediationHandler.processMessage
(InterfaceMediationHandler.java:605)

at com.ibm.ws.sca.internal.message.impl.
MessageDispatcherImpl.processMessage
(MessageDispatcherImpl.java:465)

at com.ibm.ws.sca.internal.message.impl.
ManagedMessageImpl.process(ManagedMessageImpl.java:487)

at com.ibm.ws.sca.internal.async.impl.
AbstractAsyncInboundHandler.processMessage
(AbstractAsyncInboundHandler.java:111)

at com.ibm.wsspi.sca.async.bean.impl.
ServiceSIBusMessageBean.processMessage
(ServiceSIBusMessageBean.java:213)

at com.ibm.wsspi.sca.async.bean.impl.
ServiceSIBusMessageBean.access$000
(ServiceSIBusMessageBean.java:45)

at com.ibm.wsspi.sca.async.bean.impl.
ServiceSIBusMessageBean$1.onMessage
(ServiceSIBusMessageBean.java:62)

at com.ibm.wbiserver.manualrecovery.ejb.
RecoveryMessageDrivenBean.onMessage
(RecoveryMessageDrivenBean.java:167)

at com.ibm.wsspi.sca.async.bean.impl.
ServiceSIBusMessageBean.onMessage
(ServiceSIBusMessageBean.java:103)

PROBLEM CONCLUSION:                                             
The problem can be resolved by the fix.                         


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: