Question
amex
US
Last activity: 17 Jul 2017 16:01 EDT
Soap service failed with Tranport level infomration error
Hi Folks,
I am getting the folowing error while calling a soap service and with the same exact reqeust parameters things go smooth in SOAP -UI
if you have any informaiton regarding this error , please let me know
** SOAP service failed, error:Transport level information does not match with SOAP Message namespace URI
Thanks,Vijay
Hi Vijay,
What is the version of PRPC your using? Please add DEBUG to following classes below and recreate the scenario. Attach the latest PegaRULES log for review.(https://docs-previous.pega.com/how-debug-soap-connect-failure-resourceunavailableexception-or-remoteapplicationexception).
Rule_Obj_Activity.InvokeAxis2.Rule_Connect_SOAP.Action
com.pega.pegarules.integration.internal.ServiceHelper
com.pega.pegarules.integration.internal.util.SOAPUtils
Regards,
Adi
Updated: 17 Mar 2015 15:32 EDT
Hi Vijay,
You are using WS-Security profile to secure Connect-SOAP. Are you passing the WS-Security on SOAPUI and passing the same keystore as you are doing in Pega?
This is the line where the failure is occurring:
2015-03-17 11:44:05,913 [ WebContainer : 9] [ STANDARD] [ ] (_Data_InqCallerListSvc_.Action) ERROR - WCC getCustomerReferenceNumber Service Error
Searching for occurrences of getCustomerReferenceNumber activity above in the logs:
Hi Vijay,
You are using WS-Security profile to secure Connect-SOAP. Are you passing the WS-Security on SOAPUI and passing the same keystore as you are doing in Pega?
This is the line where the failure is occurring:
2015-03-17 11:44:05,913 [ WebContainer : 9] [ STANDARD] [ ] (_Data_InqCallerListSvc_.Action) ERROR - WCC getCustomerReferenceNumber Service Error
Searching for occurrences of getCustomerReferenceNumber activity above in the logs:
2015-03-17 06:50:13,567 [ WebContainer : 1] [ STANDARD] [] ( internal.services.ServiceAPI) ERROR - SOAP service [CustomerReferenceNumberDetails][Services][getCustomerReferenceNumber] failed:Inbound data mapping failed:com.pega.pegarules.pub.services.ServiceException: Inbound data mapping failed at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.mapInputData(ServiceAPI.java:1502) at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.processSimulation(ServiceAPI.java:1963) at com.pega.pegarules.integration.engine.internal.services.ServiceSimulator.processServiceSimulation(ServiceSimulator.java:685) at com.pega.pegarules.integration.engine.internal.services.ServiceSimulator.invokeServiceSOAP(ServiceSimulator.java:185) at com.pega.pegarules.integration.engine.internal.services.ServiceSimulator.execute(ServiceSimulator.java:149) at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.executeServiceSimulation(PRServiceUtils.java:1599) at com.pegarules.generated.activity.ra_action_execute_2c62a816d30b81da73aab99e7d88cbbb.step7_circum0(ra_action_execute_2c62a816d30b81da73aab99e7d88cbbb.java:741) at com.pegarules.generated.activity.ra_action_execute_2c62a816d30b81da73aab99e7d88cbbb.perform(ra_action_execute_2c62a816d30b81da73aab99e7d88cbbb.java:252) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3097) at com.pegarules.generated.activity.ra_action_runruleexecute_c0b5c88c29a0af365bf033118a9868d2.step12_circum0(ra_action_runruleexecute_c0b5c88c29a0af365bf033118a9868d2.java:1574) at com.pegarules.generated.activity.ra_action_runruleexecute_c0b5c88c29a0af365bf033118a9868d2.perform(ra_action_runruleexecute_c0b5c88c29a0af365bf033118a9868d2.java:292) ... at com.pega.pegarules.internal.web.servlet.WebStandardBoot.doPost(WebStandardBoot.java:118) at javax.servlet.http.HttpServlet.service(HttpServlet.java:738) at javax.servlet.http.HttpServlet.service(HttpServlet.java:831) ... at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:84) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1660) Caused by: com.pega.pegarules.pub.PRException: Caught exception parsing XML stream From: (HCC25273986C18C4FFF738F96024211D4: Proprietary information hidden) at com.pega.pegarules.integration.engine.internal.mapping.xml.XMLParserBase.parseDocument(XMLParserBase.java:512) at com.pega.pegarules.integration.engine.internal.mapping.xml.XMLParserBase.parseDocument(XMLParserBase.java:498) at com.pega.pegarules.integration.engine.internal.mapping.ParseRuleUtils.invokeXMLParseRuleWithParam(ParseRuleUtils.java:1257) at com.pega.pegarules.integration.engine.internal.ServiceHelper.applyXMLParseRuleWithParam(ServiceHelper.java:5988) at com.pega.pegarules.integration.engine.internal.ServiceHelper.setInboundDataValue(ServiceHelper.java:1691) at com.pega.pegarules.integration.engine.internal.ServiceHelper.mapInboundData(ServiceHelper.java:1333) at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.mapInputData(ServiceAPI.java:1426) ... 72 more Caused by: org.xml.sax.SAXParseException: Premature end of file. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at com.pega.pegarules.integration.engine.internal.mapping.xml.XMLParserBase.parseDocument(XMLParserBase.java:507) ... 78 more
Question:
1. Did you start seeing these error recently after making some changes, you might be aware of?
2. Did you use the Integration and Metadata wizard to generate the mapping and activities?
3. It seem there is an issue with your parse XML rule, can you run the parse XML rule manually and paste the SOAP request and see if you get the same error?
4. Are you passing any special character(non-ASCII or non-UTF8) to the SOAP request?
Regards,
Adi
amex
US
Hi Guys,
I figured out the problem. when pega calls the service it puts the Content-Type as application/soap+xml since it is soap 1.2 but when the service provider responded back they modified as Content-Type to text/xml , because of that invoke axis failed
even though there was response it never started to parse.
now the issue is fixed, i appreciate everyone who take some time to look into this issue and tried to help me.
Thanks,
Vijay
amex
US
sure, the issue was in service not in PRPC. when pega calls the service it sends the contentype as application/soap+xml and the service prvider should have used the same value when responded back instead he used his own tag that was text/xml and it was not the right type for SOAP 1.2 . so after receiving the response there was an exception at the invoke axis activity and this error was displayed. the only thing from pega could have been better is that though the response was received there was not indication of it.
hope this helps. let me know if you have any questions.
thanks,
Vijay