Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException on Test

Tom HenricksenFeb 15 2016 — edited Feb 26 2020

I am getting a oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException when I test a composite that is trying to call PeopleSoft.

When I test the composite I get a fault and the following message: oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server :

PeopleSoftServiceListeningConnector:HTTPRequest : SAXException occurred while parsing the SOAP Document. SAXExceptionMessage : The prefix "xmlns" cannot be bound to any namespace explicitly; neither can the namespace for "xmlns" be bound to any prefix explicitly.

I went through the log files and found the following in the WLS_SOA1-diagnostic.log

Message got FabricInvocationException, Cikey=661168, FlowId=480537, Current Activity Key=661168-BpInv0-BpSeq1.7-2, Current Activity Label=InvokeCreateItem, ComponentDN=ItemServices/PPLSFT_CRUD_Item_ABCS_prov!1.0*soa_aaaac9ea-a659-4215-b489-4c06885d5e6c/PPLSFT_CRUD_Item_ABCS_prov Supplemental Detail oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : PeopleSoftServiceListeningConnector:HTTPRequest : SAXException occured while parsing the SOAP Document. SAXExceptionMessage : The prefix "xmlns" cannot be bound to any namespace explicitly; neither can the namespace for "xmlns" be bound to any prefix explicitly. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1752) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invokeOneWay(DispatchImpl.java:1993) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invokeOneWay(OracleDispatchImpl.java:113) at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:602) at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.processOutboundMessage(WebServiceExternalBindingComponent.java:342) at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.sendSOAPMessage(WebServiceExternalBindingComponent.java:1445) at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.post(WebServiceExternalBindingComponent.java:1144) at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler.doPost(AsynchronousMessageHandler.java:144)

Another developer suggested I look at the WSDLs and when I did I noticed the one in MDS was slightly different than what is in the Service. I updated the MDS version and transferred to our development environment and I still see the same issue.

Any suggestions?

Thanks,

Tom

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 15 2016
Added on Feb 15 2016
2 comments
1,978 views