Fix (APAR):  PH13533

Status:  Fix

Release:  8.5.5.15

Operating System:  AIX,HP-UX,IBM i,Inspur K-UX,Linux,OS X,Solaris,Windows,iOS,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  260851

Date: 2019-06-24

Abstract:  web service request containing ws-at context fails if provider web service is configured to support ws-rm

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

ERROR DESCRIPTION:
When processing an inbound Web Service request with a WS-AT     
Context, processing fails with a java.lang.ClassCastException   
when marshalling the response.                                  
                                                                
The call stack associated with the error is of the form:        
                                                                
AxisEngine    E org.apache.axis2.engine.AxisEngine receive      
Sandesha2 got an exception when processing an out message:      
java.lang.ClassCastException:                                   
org.apache.axiom.om.impl.llom.OMElementImpl incompatible with   
org.apache.axiom.soap.SOAPHeaderBlock.                          
                                 org.apache.axis2.AxisFault:    
Sandesha2 got an exception when processing an out message:      
java.lang.ClassCastException:                                   
org.apache.axiom.om.impl.llom.OMElementImpl incompatible with   
org.apache.axiom.soap.SOAPHeaderBlock.                          
 at                                                             
org.apache.sandesha2.handlers.SandeshaOutHandler.invoke(Sandesha
OutHandler.java:232)                                            
 at                                                             
org.apache.axis2.handlers.AbstractHandler.invoke_stage2(Abstract
Handler.java:133)                                               
 at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:343) 
 at org.apache.axis2.engine.Phase.invoke(Phase.java:313)        
 at                                                             
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:372)  
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:537)
 at                                                             
org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWS
MessageReceiver.java:220)                                       
 at                                                             
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:212) 
 at                                                             
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPo
stRequest(HTTPTransportUtils.java:172)                          
 at                                                             
com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(WASAxis
2Servlet.java:1632)                                             
...                                                             

LOCAL FIX:

PROBLEM SUMMARY:

USERS AFFECTED:
 WebSphere Application Server users of Web
Services Atomic Transactions

PROBLEM DESCRIPTION:
Provider side processing of a Web
Service request containing a WS-AT
Context fails with
java.lang.ClassCastException

RECOMMENDATION:
None

If a Web Service provider is configured to support both
WS-Atomic Transactions and WS-ReliableMessaging then a
java.lang.ClassCastException occurs when the provider is
processing the response to a request containing a WS-AT
context.
It should be noted that WS-RM and WS-AT cannot be used on the
same request by design, however it should be possible for a
Web Service provider to be configured to support both WS-AT
and WS-RM so that either of those qualities of service are
available on a mutually exclusive basis.
The ClassCastException occurred because the WS-AT component
inserted a plain OMElement directly into the SOAPHeader rather
than a SOAPHeaderBlock.  Later processing by the WS-RM
component cast the SOAPHeader's child directly to a
SOAPHeaderBlock.

PROBLEM CONCLUSION:
The WS-AT component was modified to add a SOAPHeaderBlock,      
rather than a plain OMElement, to the SOAPHeader.               
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix packs 8.5.5.16 and 9.0.5.1.  Please refer to the            
Recommended Updates page for delivery information:              
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  Fix applies to Editions:
_X_ Application Server (Express or BASE)
_X_ Network Deployment (ND)
__ Liberty Core
__ Edge Components
_X_ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: