cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Error:

Go to solution
Former Member

on ‎02-27-2014 6:17 AM

0 Kudos

Error:

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

   <SOAP:Body>

      <SOAP:Fault>

         <faultcode>SOAP:Client</faultcode>

         <faultstring>Server Error</faultstring>

         <faultactor>http://sap.com/xi/XI/Message/30</faultactor>

         <detail>

            <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30">

               <SAP:Category>XIProtocol</SAP:Category>

               <SAP:Code area="PARSING">GENERAL</SAP:Code>

               <SAP:Stack>null; nested exception caused by:

com.sap.aii.adapter.soap.web.SOAPHandlerException ["Invalid XI message"]

at com.sap.aii.adapter.soap.web.SOAPHandler.setup(SOAPHandler.java:380)

at com.sap.aii.adapter.soap.web.SOAPHandler.channelSetup(SOAPHandler.java:258)

at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:490)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)

at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)</SAP:Stack>

            </SAP:Error>

         </detail>

      </SOAP:Fault>

   </SOAP:Body>

</SOAP:Envelope>

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

iaki_vila
Active Contributor
‎02-27-2014 7:20 AM
0 Kudos

Hi Mohammed,

If you have the endpoint wsdl try to compare your WS request with the XML generated by external tool like SOAPui.

I have a different approach to Indrajit, i prefer in this cases to construct the SOAP envelope manually by XSL (I sometimes set the exact request with the payload "hardcoded" to be send to the endpoint), i set the check Do Not Use SOAP envelope and i use the parameter mentioned by Indrajit in order to have the exactly response of the endpoint.

Regards.

Show replies
Show replies
Former Member
‎02-27-2014 9:58 AM
0 Kudos


Thanks Vila,

I my case i dont need the response as third party is not ready now,I just want to check request mapping along with validating  the conditions given in Interface determination and then the message fails.

My sender channel is SOAP at SAP side and I use XI 3.0 message protocol.

and I dont see "Do Not Use SOAP envelope" box to check.

Please suggest.

thanks,

Former Member
‎02-27-2014 10:28 AM
0 Kudos

Hi

So your scenario is ECC to SOAP??

Former Member
‎02-27-2014 10:32 AM
0 Kudos

yes

Former Member
‎02-27-2014 11:52 AM
0 Kudos

Hi Gouse

You cannot use Soap UI to test the "ECC to SOAP" scenario as you sender is ECC.

Even though you are using SOAP Adapter for connecting to ECC systems. You will be using Message protocol as XI. This is equivalent to XI adapter, so SOAP UI cannot be used.

Regards

Osman Abdul Aziz Jabri

Answers (1)

Answers (1)

Former Member
‎02-27-2014 6:22 AM
0 Kudos

This an synchronous scenario.am not able to see the error logs in Communication Channel and Message monitoring of SAP PI 7.31.

The above error when I try to  trigger the message through soap UI/WSNavigator .

I tried:

Configuring SAP PI: NWA -> Configuration -> Infrastructure -> Java System Properties -> Services -> XPI Service: Messaging System, set property messaging.SyncMessageRemover.removeBody = false.

Any Ideas are welcome.

thanks in advance

Show replies
Show replies
Former Member
‎02-27-2014 6:26 AM
0 Kudos

Hello,

What's ur target system?

I think u are not receiving response properly.

Thanks

Amit Srivastava

Former Member
‎02-27-2014 7:11 AM
0 Kudos

Hi,

Looks like the web service has return the fault exception because you are sending wrong data to web service.

Please make sure that you haven't add the below parameter in your SOAP communication channel

XMBWS.NoSOAPIgnoreStatusCode = true

Former Member
‎02-27-2014 7:19 AM
0 Kudos

Thanks for your reply Amit.

My target System is thrid party ,but anyways am not  testing end to end .

Am checking till PI my mapping and all.

Thanks,

Mohammed Gouse

Former Member
‎02-27-2014 7:29 AM
0 Kudos

Hello,

This means just to check ur mapping (request and response) u are using SOAP UI, but what abt third party system connectivity?

If ur receiver system is not sending any response then how can u test ur interface (and mapping also). Correct me if i misunderstood u.

BTW, if u just want to test ur mapping then use ESR and test it locally.

Thanks

Amit Srivastava

Former Member
‎02-27-2014 9:31 AM
0 Kudos


Hi Indrajit ,

Thanks for your reply.

I have not added the below parameter in the SOAP Channel.

Thanks,

Mohammed Gouse

Former Member
‎02-27-2014 10:01 AM
0 Kudos

Hi Amit,

I want to test only my req mapping along with the conditions given in Interface Determination .

Thanks,

Mohammed Gouse

Former Member
‎02-27-2014 10:38 AM
0 Kudos

Hello,

>>My sender channel is SOAP at SAP side and I use XI 3.0 message protocol.

For testing with SOAP UI u have to use soap sender channel with transport protocol as "soap 1.1".

secondly, in a sync scenario u are using conditions at ID level? Could u briefly explain what u want to achieve?

Thanks

Amit Srivastava

Ask a Question