Fixes are available
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
We are receiving a SOAPFaultException when using a RPC-LIT web service with WS-Addressing applied. To recreate this problem: 1. Build a RPC-Lit web service and client using fragmented wsdl document (i.e. - The wsdl is split into multiple files using different namespaces) 2. Attach WS-Addressing default It should be noted that the client and service work fine when there is no policy attached. The following error occurs after attaching WS-Addressing default: Result: 3/10/09 18:17:59:733 EDT] 00000035 AddressingFau W org.apache.axis2.addressing.AddressingFaultsHelper triggerActionNotSupportedFault triggerActionNotSupportedFault: messageContext: [MessageContext: logID=urn:uuid:1B76635B6BBCE94E691236723509778] problemAction: http://example.org/action/SignatureRpcInEmpty [3/10/09 18:17:59:749 EDT] 0000002d SystemOut O >>> EXCEPTION javax.xml.ws.soap.SOAPFaultException: The [action] cannot be processed at the receiver. This is the Soap message coming back from the server: <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:Action> http://www.w3.org/2005/08/addressing/fault</wsa:Action><wsa: RelatesTo>urn:uuid:A211325CB365371B581236383239106</wsa:RelatesT o></soapenv:Header><soapenv:Body><soapenv:Fault> <soapenv:Code><soapenv:Value>soapenv:Sender</soapenv:Value><soap env:Subcode><soapenv:Value xmlns:wsa="http://www.w3.org/2005/08/a ddressing">wsa:ActionNotSupported</soapenv:Value></soapenv:Subco de></soapenv:Code><soapenv:Reason><soapenv:Text xml:lang="en-US">The [action] cannot be processed at the receiver.</soapenv:Text></soapenv:Reason><soapenv:Detail><wsa:Pr oblemAction xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:Action>htt p://example.org/action/SignatureRpcInEmpty</wsa:Action></wsa:Pro blemAction></soapenv:Detail></soapenv:Fault></soapenv:Body></soa penv:Envelope>
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 users * * of JAX-WS with WS-Addressing applied * **************************************************************** * PROBLEM DESCRIPTION: SOAPFaultException received * * when using a rpc/literal web * * service with WS-Addressing applied * **************************************************************** * RECOMMENDATION: Install a fixpack containing this APAR * **************************************************************** The user is receiving a SOAPFaultException when using a rpc/literal web service with WS-Addressing applied. These are the steps they are using to recreate the problem: 1. Build a RPC-Lit web service and client using fragmented wsdl document (i.e. - The wsdl is split into multiple files using different namespaces) The client and service will work fine at this point. Then, when WS-Addressing is applied the following error will occur: Result: 3/10/09 18:17:59:733 EDT] 00000035 AddressingFau W org.apache.axis2.addressing.AddressingFaultsHelper triggerActionNotSupportedFault triggerActionNotSupportedFault: messageContext: [MessageContext: logID=urn:uuid:1B76635B6BBCE94E691236723509778] problemAction: http://example.org/action/SignatureRpcInEmpty [3/10/09 18:17:59:749 EDT] 0000002d SystemOut O >>> EXCEPTION javax.xml.ws.soap.SOAPFaultException: The [action] cannot be processed at the receiver. The problem occurs during the invocation of a deployed Web service (in particular an rpc/Literal defined service with a multi-file WSDL definition which has multiple, distinct targetNamespaces) with WS-Addressing enabled. The server may respond with "The [action] cannot be processed at the receiver" even though the WSDL definition and service implementation are correct. The root of the problem is the JAX-WS runtime is using the wrong namespace on the operation element in the sent message.
Problem conclusion
The target namespace of the operation (if not specified) should be obtained from the parent web service endpoint interface class. Due to an error in the JAX-WS runtime, this defaulting code was incorrect. The JAX-WS runtime is changed to match the defaulting rule. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK85092
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-21
Closed date
2009-05-13
Last modified date
2009-05-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
25 October 2021