Fixes are available
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.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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
When a WebService client running on .NET calls a WebService provider residing on WebSphere Process Server, which has been migrated from version 6.2 to version 7.0.0.1, running on top of WebSphere Application Server version 7.0.0.7, using Microsoft Distributed Transaction Coordinator, this error occurs: SystemEngineR E com.ibm.ws.webservices.sysengine.SystemEngineRouter doPost WSWS3227E: Error: Exception: javax.xml.rpc.JAXRPCException: WSWS3122E: Error: Could not find service services/WSATFaultPort referenced in URI /_IBMSYSAPP/wsatfault/services/WSATFaultPort at com.ibm.ws.webservices.handlers.WSURLMapper.preHandleIncoming(WS URLMapper.java:126) at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandlerChain .preHandleIncoming(JAXRPCHandlerChain.java:241) at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler.invo keServerIncomingPreHandler(JAXRPCHandler.java:522) at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler$1.pr eHandleIncoming(JAXRPCHandler.java:402) at com.ibm.ws.webservices.engine.PivotHandlerWrapper.preHandleIncom ing(PivotHandlerWrapper.java:553) at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHa ndlerWrapper.java:184) at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServic esEngine.java:336) at com.ibm.ws.webservices.sysengine.SystemEngineRouter.doPost(Syste mEngineRouter.java:141) at com.ibm.ws.soap.container.component.SOAPContainerChannelComponen tImpl.handleRequest(SOAPContainerChannelComponentImpl.java:176) at com.ibm.ws.soapchannel.acceptor.SOAPAcceptorConnectionLink.run(S OAPAcceptorConnectionLink.java:294) at com.ibm.ws.soapchannel.acceptor.SOAPAcceptorConnectionLink.reque stReady(SOAPAcceptorConnectionLink.java:266) at com.ibm.ws.soapchannel.acceptor.SACReadCallback.readRequest(SACR eadCallback.java:212) at com.ibm.ws.soapchannel.acceptor.SOAPAcceptorConnectionLink.ready (SOAPAcceptorConnectionLink.java:194) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr imination(HttpInboundLink.java:455)
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All IBM WebSphere Application Server V7.0 * * users of Web Services - Atomic * * Transactions (WS-AT) * **************************************************************** * PROBLEM DESCRIPTION: Server cannot process an incoming * * WS-AT SOAP fault because service * * services/WSATFaultPort cannot be found. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a Web Service client attempts to send a WS-AT SOAP fault to a Web Service provider on WebSphere Application Server, the following error is logged : SystemEngineR E com.ibm.ws.webservices.sysengine.SystemEngineRouter doPost WSWS3227E: Error: Exception: javax.xml.rpc.JAXRPCException: WSWS3122E: Error: Could not find service services/WSATFaultPort referenced in URI /_IBMSYSAPP/wsatfault/services/WSATFaultPort at com.ibm.ws.webservices.handlers.WSURLMapper.preHandleIncoming(WS URLMapper.java:126) at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandlerChain .preHandleIncoming(JAXRPCHandlerChain.java:241) at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler.invo keServerIncomingPreHandler(JAXRPCHandler.java:522) at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler$1.pr eHandleIncoming(JAXRPCHandler.java:402) at com.ibm.ws.webservices.engine.PivotHandlerWrapper.preHandleIncom ing(PivotHandlerWrapper.java:553) at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHa ndlerWrapper.java:184) at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServic esEngine.java:336) at com.ibm.ws.webservices.sysengine.SystemEngineRouter.doPost(Syste mEngineRouter.java:141) at com.ibm.ws.soap.container.component.SOAPContainerChannelComponen tImpl.handleRequest(SOAPContainerChannelComponentImpl.java:176) at com.ibm.ws.soapchannel.acceptor.SOAPAcceptorConnectionLink.run(S OAPAcceptorConnectionLink.java:294) at com.ibm.ws.soapchannel.acceptor.SOAPAcceptorConnectionLink.reque stReady(SOAPAcceptorConnectionLink.java:266) at com.ibm.ws.soapchannel.acceptor.SACReadCallback.readRequest(SACR eadCallback.java:212) at com.ibm.ws.soapchannel.acceptor.SOAPAcceptorConnectionLink.ready (SOAPAcceptorConnectionLink.java:194) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr imination(HttpInboundLink.java:455) This was because the WSDL that described the WS-AT fault address location had an incorrect service name.
Problem conclusion
The service name in the WSDL describing the WS-AT fault address has been corrected. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.13. 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
PM15539
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-05-31
Closed date
2010-07-22
Last modified date
2010-07-22
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
24 October 2021