Oracle.fabric.common.FabricInvocationException: Unable To Invoke Endpoint URI
(Doc ID 2741569.1)
Last updated on SEPTEMBER 24, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version, Fabric
oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI
Our Application is integrated with Third pary service using Oracle SOA suite. Third party is sending the below business exception but SOA is decoding that as a remote fault.
SOA is throwing below SOAP fault for the above business exception.
oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI "https://URL:PORT/foil/webservices/manageinterest" successfully due to: Could not determine soap fault from message oracle.j2ee.ws.saaj.soap.soap11.Message11@19718d26
We have added Oracle log policy to capture SOAP request and response . In the SOAP response we are able to see the business exception sent by third party service.
ERROR
-----------------------
** MaxThreadsConstraints: 150
** Total dispatcher messages scheduled for processing: 0
** Total number of threads processing dispatcher messages: 1
** Max Heap size: 1552416768
** Free Heap size: 471996936 oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI "https://[SERVICE_URL]:[SERVICE_PORT]/foil/webservices/manageinterest" successfully due to: Could not determine soap fault from message oracle.j2ee.ws.saaj.soap.soap11.Message11@36b4b261
at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:710)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.processOutboundMessage(WebServiceExternalBindingComponent.java:373)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.sendSOAPMessage(WebServiceExternalBindingComponent.java:1577)
...
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)
Caused by: javax.xml.ws.WebServiceException: Could not determine soap fault from message oracle.j2ee.ws.saaj.soap.soap11.Message11@36b4b261
at oracle.webservices.SOAPFaultException.getFault(SOAPFaultException.java:67)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1833)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:1408)
at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:238)
at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:109)
at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:646)
... 58 more
Caused by: javax.xml.ws.WebServiceException: Could not determine soap fault from message
at oracle.webservices.SOAPFaultException.getFault(SOAPFaultException.java:64)
... 63 more
]]
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |