SAP WebAS SOAP runtime cannot recognize empty soap:Header /soap:Header

Hi expert,
I 'm trying to send a SOAP request to SAP WebAS ABAP. I found that if the WebAS cannot recongize <soap:Header/> but not <soap:Header></soap:Header>. Any idea? Is it a bug? Thanks.
Regards,
Ken

Resolved with the following blog
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

Similar Messages

Webi Reports failing -Cannot execute empty query

Intermittent problem affecting all Webi reports in the SAP BI system .
This affects all Release 1 and Release 2 Webi reports
When the user tries to run the report, an error message appears with the message "Cannot execute empty query. (QTJ00521)"
User can close the report and try to run it again - the report may execute properly the second time.
This problem started in production at R2 go live. It is affecting both R1 and R2 webi reports.
It cannot be reproduced in lower environments.

Hi,
Check attached SAP note if this is relevant for your issue.As per this SAP note this happens when query stripping option is checked.If this is checked then uncheck and try.
1936256 - Error "Cannot execute empty query. (QTJ 00521)(WIS 00000)" when refreshing Web Intelligence report
Amit

SOAP Runtime exception using Adobe Document Services

Hi all,
we have an intermittent problem with the following scenario:
ECC6 ABAP system which runs our Payroll.
Separate JAVA instance running our SAP portal and Adobe Document Services.
SM59 connection from the ABAP system to the portal server where ADS runs. Connection via port 5554.
We have written our own transaction ZPAYSLIP which allows users to view and print their payslips using ADS. This transaction uses a program generated in transaction HRFORMS.
Periodically, this transaction will fail with the following error at the bottom of the user's screen:
ADS: SOAP Runtime Exception: CSoapExceptionTransport: (100101SOAP Framework error: SOAP Runtime Exception)
A lot of the problem is that this issue is sporadic and difficult to reproduce. Whenever it has been reported to me and I try to reproduce the error I am unable to. A test of the SM59 connection shows everything is OK and if I ask the user to retry it, it will work.
I have asked our network team to check the connection between the 2 servers at the time when the error happens, but they cannot find any problems with connectivity between them, and yet it looks to me like the problem is a temporary loss of connectivity or that ADS somehow becomes temporarily unavailable.
I have done the checks as referred to in sapnote 944221 (many times!) but that all checks out OK.
We have logged a call with SAP, but they haven't really come up with a solution apart from restarting the JAVA engine which is not what we want to have to do.
We also experience the same error from time to time with some of our portal functionality which also uses ADS.
Has anyone experienced a similar error or have any suggestions as to how we might fix this?
Regards....John

Hi,
We have encountered a very similar issue after patching our dual stack ECC to NW23/ERP603 sp8. After first correcting it by routing the ADS calls directly to the server (and not through the web dipspatcher), we then updated our SAP Web Dispatcher to a newer version and this seems to have resolved it while maintaining the necessary load-balancing functionality of the web dispatcher.
Hope this helps.
Ruben

SOAP Responce cannot be decoded after during a long web service exection

I have an AIR application.
I am using the spark web service and i have set up a fualt handler and set the requestTimeout to 0.
I call an opertaion that calls a .Net web service.
Inside that .Net web service i run a very heafty SQL using ADO and then i take the results from the SQL statment and I use those results to make an excel spreadseeht and saved on the machine running the webservice.
This web service ran by itself can easily take up to two minutes to run (which is very acceptable given the nature of the query), and I would like the AIR application to just continue to sit there and wait for it to complete (also acceptable).
Even with the request timeout set 0 i receive a "SOAP Responce cannot be decoded" fault from the webservice before the web service is even done running. Why is this happening?
I've run several debuggers to make sure the info to the .Net web service is correct, I've stepped through the entire web service piece by piece and no exceptions are thrown during its execution. It just takes a long time to perform and the fault occurs right in the middle of the execution of web service.
I've also had this happen when i'm debugging some of my other web serivces. If a breakpoint is hit in visual studio in my webservice and i do my thing and step through stuff blah blah blah standard debugging stuff, the same thing will happen a fault will be hit before the webservice is done executing.
Please help.

I'm not sure what the deal is between Flex/AIR and Visusal Studios, but i descided to publish my webservices and point the wsdl there instead of using the visual studio generated one.
AND BEHOLD
I't worked and worked much much faster than i was anticipating.
So i'll just chalk it up to poor communication between FLEX and VS. But if anybody knows a more complete answer I would still love to hear it.

Web Service Proxy error: "No operation found using soap keys"

I'm trying to use the new tools, and having a little trouble. Not many results when searching for this error message.
I have developed and deployed a new Java web service proxy using the outside-in approach according to the [help docs|http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/7f2fef88190ad3e10000000a11466f/frameset.htm] (PI 7.1 SP07, NWDS 7.1 CE SP09 PAT0000). Started with a Service interface in ESR, then generated a java bean skeleton into a new EJB project in NWDS, then wrote business logic and deployed.
When I test the web service (with 3 different SOAP test clients) I get the same error, below:
     <faultstring>com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException:
No operation found using soap keys [], [spmat_jdbc_receiver_proxy]. InterfaceMapping Object class:
com.sap.engine.services.webservices.espbase.mappings.InterfaceMapping mappings: {BindingQName=
{urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_ProxyBinding, BindingType=Soap, PortTypeQName=
{urn:nexeninc:pi:ll:spmat:100}SI_I_Sync_SPMAT_JDBC_Receiver_Proxy, JAXWSInterface=true, InterfaceMappingID=-
27e4d529:127632b5c52:-7ebb}.</faultstring>
My service endpoint interface looks like this (unimportant lines removed):
package nexeninc.pi.ll.spmat._100;
@javax.jws.WebService(name = "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy", targetNamespace = "urn:nexeninc:pi:ll:spmat:100")
@javax.jws.soap.SOAPBinding(parameterStyle = javax.jws.soap.SOAPBinding.ParameterStyle.BARE, style = javax.jws.soap.SOAPBinding.Style.DOCUMENT, use = javax.jws.soap.SOAPBinding.Use.LITERAL)
public interface SIISyncSPMATJDBCReceiverProxy {
@javax.jws.WebMethod(operationName = "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy", action = "http://sap.com/xi/WebService/soap1.1")
@javax.jws.WebResult(name = "spmat_jdbc_receiver_proxy_response", targetNamespace = "", partName = "spmat_jdbc_receiver_proxy_response")
public generated.SpmatJdbcReceiverProxyResponse siISyncSPMATJDBCReceiverProxy(@javax.jws.WebParam(name = "spmat_jdbc_receiver_proxy", targetNamespace = "", partName = "spmat_jdbc_receiver_proxy") generated.SpmatJdbcReceiverProxy spmat_jdbc_receiver_proxy);

(continued from above post)
And my implementation bean looks like this (unimportant lines removed):
package nexeninc.pi.ll.spmat._100;
@SessionHandlingDT(enableSession = false)
@AuthenticationDT(authenticationLevel = AuthenticationEnumsAuthenticationLevel.BASIC)
@TransportGuaranteeDT(level = TransportGuaranteeEnumsLevel.NONE)
@WebService(serviceName = "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy_Service", portName
= "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy_Port", endpointInterface
= "nexeninc.pi.ll.spmat._100.SIISyncSPMATJDBCReceiverProxy", targetNamespace = "urn:nexeninc:pi:ll:spmat:100", wsdlLocation
= "META-
INF/wsdl/nexeninc/pi/ll/spmat/_100/SI_I_Sync_SPMAT_JDBC_Receiver_Proxy/SI_I_Sync_SPMAT_JDBC_Receiver_Proxy.wsdl")
@Stateless
public class SIISyncSPMATJDBCReceiverProxyImplBean {
     @RelMessagingNW05DTOperation(enableWSRM = false)
     public generated.SpmatJdbcReceiverProxyResponse siISyncSPMATJDBCReceiverProxy(
               generated.SpmatJdbcReceiverProxy spmat_jdbc_receiver_proxy) {
          System.out.println("Starting siISyncSPMATJDBCReceiverProxy.");
When we first created the new endpoint in NWA, we tried asigning a new name for both "Service Endpoint Name" and "In New Service", and we received this error.
We then deleted the endpoint and created another new one, setting "Service Endpoint Name" to match the portName in the implementation bean: "SI_I_Sync_SPMAT_JDBC_Receiver_Proxy_Port", but that didn't work either. The only option we enabled in the endpoint was HTTP authentication: User ID/Password.
My ejb-j2ee-engine.xml and application-j2ee-engine.xml are both empty (but they exist).
I am new to EJBs and JAX-WS so hopefully it's something simple. All help appreciated!
Apologies for the long (and wide) post.
- Rob

SOAP Runtime exception: 1023 method IF_SOAP_TRANSPORT_BINDING~receive

SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: HTTP COMMUNICATION FAILURE")
SOAP Runtime exception: 1023 occured in method IF_SOAP_TRANSPORT_BINDING~receive of class CL_SOAP11_HTTP_TPBND at position 1
Getting the error above when making a web service call to external web service. Used to work all the time. Getting the error all the time now.

Hi.
Check the response. Sometimes this error occurs due to an empty response.
Regards.
Rafael Rojas.

Adobe document service error: SOAP Runtime Exception

Hello,
I am trying to test an Adobe Form created using the ABAP workbench SFP transaction, and getting the following error.
<b>Adobe document services error: SOAP Runtime Exception: CSoapExceptionTransport : (100101)</b>
These are the steps I am using.
1. Call SFP transaction and select an ADOBE Form.
2. Function key F8 to test
3. Select the Output device and do "Print Preview"
Our configuration is : WAS 6.40 SP11 and corresponding ADS level. We used the standard SAP ADS configuration guide to setup.
Thanks in advance for any reply.
Regards,
PK

Hi PK
it looks like you have a problem with either your Adobe document services or your RFC configuration. In the current ADS Configuration Guide in the SAP Service Marketplace, you find a configuration quick test in chapter 3.4. The results should tell you if this is the issue.
There are 2 tests you can run:
A. Checking the User and Password
This is a small test where you can check that your entries for user, security role, and passwords are correct.
Procedure:
1. Enter the following URL in your web browser:
http://<server>:<port>/AdobeDocumentServices/Config
where <server> is the name of the J2EE engine where the Adobe document services are installed and <port> is the port of the J2EE engine.
Note that the entries in the URL are case-sensitive.
2. The web page of the web service AdobeDocumentServices is displayed. Choose Test.
3. Choose rpdata(test.) .
4. Choose the Send button without entering any parameters.
5. Enter the same user name and password as given in the configuration steps earlier.
6. Choose Submit.
If the configuration is correct, you get the information about the Version number in the response area.
If the configuration settings are not correct, the page does not change and Submit still appears.
B. Checking the ABAP Connection
This is a small test for checking the RFC destination you have created.
Procedure
1. Log on to your SAP system.
2. Call transaction SE38
3. Enter the name of the test report: FP_PDF_TEST_OO.
4. Choose Execute (F8)
If the configuration is correct, you get the Version Information.
If the configuration is not correct, you get a dialog box with fields for user and password. Check your configuration settings and also the entries you made when creating the ABAP connection.
Hope this helps.
Kind regards,
Markus Meisl
SAP NetWeaver Product Management

XML integration: SOAP Runtime Exception

Hi, and a happy new year to all of you.
I'm quite in trouble right now: I'm trying to process an XML flow into BW, but I receive the following error when trying:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>Internal Server Error</faultstring>
<detail>SOAP Runtime Exception: CSoapExceptionInternal : XML kernel processor cannot prepare function call ( kernel rc=2 ) </detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body></SOAP-ENV:Envelope>
The strangest thing is:
- I don't see any XML error
- When I try to send the flow into another system (Without the right datasource name), i get the same error
- When I add an error in my XML code, I still have the same error
- When I try another flow for another DataSource on the target system... it works quite well
It should mean that something wrong with my xml file, but I really don't see what. Could someone help me there?
<?xml version="1.0" ?>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<rfc:_-BI0_-QI6AZtX_ST_UPFRONT_TOOLS_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<DATASOURCE>6AZX_ST_UPFRONT_TOOLS</DATASOURCE>
<DATA>
    <item>
      <LONUM></LONUM>
      <DOCNUM></DOCNUM>
      <BDLST></BDLST>
      <BU></BU>
      <BD></BD>
      <PARZC></PARZC>
      <COUNTRY></COUNTRY>
      <CREATEDON></CREATEDON>
      <DOCRY></DOCRY>
      <SOLDNUM>1000000001</SOLDNUM>
      <CUACCREQ></CUACCREQ>
      <CUCTAGGN></CUCTAGGN>
      <CUPOLAMD></CUPOLAMD>
      <CPOD></CPOD>
      <BPBSTKD>TESTLFH210</BPBSTKD>
      <CPORCVD></CPORCVD>
      <CAEATBPD></CAEATBPD>
      <DTCAED></DTCAED>
      <LABPD></LABPD>
      <LAEDCAED></LAEDCAED>
      <TVRDTD></TVRDTD>
      <FVRDTD></FVRDTD>
      <SVRDTD></SVRDTD>
      <FFHAGO>A</FFHAGO>
      <INCOCODE></INCOCODE>
      <INCOSITE></INCOSITE>
      <KTEXTSO></KTEXTSO>
      <IDNUM>10CAELA1</IDNUM>
      <IDLAV></IDLAV>
      <PARZK></PARZK>
      <TVRDTN></TVRDTN>
      <FVRDTN></FVRDTN>
      <SVRDTN></SVRDTN>
      <PARZO></PARZO>
      <ORCAT></ORCAT>
      <ORCREAV></ORCREAV>
      <PARZP></PARZP>
      <RQDATE></RQDATE>
      <FIRSTDT></FIRSTDT>
      <PARZA></PARZA>
      <SALESGRP></SALESGRP>
      <SHIPRES></SHIPRES>
      <SCTDESC></SCTDESC>
      <SELUNIT></SELUNIT>
      <SCWWBU></SCWWBU>
      <LACTV></LACTV>
      <CUPOTST></CUPOTST>
      <TOOLNUM></TOOLNUM>
      <BPROJET></BPROJET>
      <AMOUNT></AMOUNT>
      <UPDMOD></UPDMOD>
      <LBD></LBD>
      <LBGRP></LBGRP>
      <SOLANM>L-A</SOLANM>
      <SOCAENM></SOCAENM>
      <SORDNM></SORDNM>
      <FHAGO>10LA3</FHAGO>
    </item>
</DATA>
</rfc:_-BI0_-QI6AZX_ST_UPFRONT_TOOLS_RFC>
</SOAP:Body>
</SOAP:Envelope>
Thanks a lot, and please be gentle with the humble beginner I am.
Sylvain

upfront i can see one erro is that your SOAP message is not a valid XML format.
the start tag
(rfc:_-BI0_-QI6AZtX_ST_UPFRONT_TOOLS_RFC) dosent match with the end tag (rfc:_-BI0_-QI6AZX_ST_UPFRONT_TOOLS_RFC)
this may be a typo?
also since you are getting internal error, there is a chance that it might have created a ABAP dump. check in transaction ST22.
Regards
Raja

SOAP Runtime: SOAP Runtime exception: 1023 occurred in method IF_SOAP_TRANS

Hi ,
we currently have the SAP discovery system setup, i have notice that when i check the system log via sm21 , i recieve hundreds of the following error messages:
SOAP Runtime: SOAP Runtime exception: 1023 occurred in method IF_SOAP_TRANSPORT_BINDING~receive of class CL_SOAP11_HTTP_TPBND at position 1
SOAP Runtime: Exception message: SRT: Processing error in Internet Communication Framework: ("ICF Error when receivin g the response: ICM_HTTP_CONNECTION_FAILED")
Please advise where to check on resolving this error as some services donot work because of this,All services start up fine , i have also checked /nsicf and some RFC ,but have not found any thing specific.
Kind Regards
A.

Hi,
I know this question was asked a long time ago but you should check out the following note and fix to un-release the "osp" background jobs running under SM37.
Note 1113842 - Discovery System V3 Central Note

SOAP Response cannot be decoded.

Hello Everybody,
I created a simple web service in asp.net using the c# sharp language. The web service extracts data from an MS SQL Database, translates that data in to xml, assigns the xml to a string varible and returns the string varible to what ever called the service. I know the web service works becuase if you call it in a web browser at the following address http://www.jmmortimer.com/dataaccess/sqlhelper.asmx?wsdl, it will show you the xml that represents web service. Plus, I tested it by calling it in an asp.net application. However when I call it from a Flex 3 application it gives me the following error message. SOAP Response cannot be decoded. Raw response: " faultCode="DecodingError" faultDetail="null" The code that I have in Flex 3 is below. If anyone knows how to solve this problem, please let me know. Thanks in advance.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application
xmlns:mx=http://www.adobe.com/2006/mxml layout="absolute">
<mx:Script>
<![CDATA[
import mx.rpc.soap.LoadEvent;
import mx.rpc.events.ResultEvent;
private function getData(evt:LoadEvent):void
var connString:String = "Data Source=Family\SQLExpress;Initial Catalog=SDJames;User ID=sa;Password=Password1";
var storedProc:String = "GetAuxiliaries";
myService.GetDataTable(connString, storedProc)
private function resultHandler(evt:ResultEvent):void
test.text = String(evt.result);
]]>
</mx:Script>
<mx:WebService id="myService" wsdl="http://jmmortimer.com/dataaccess/sqlhelper.asmx?WSDL"
load="getData(event)" result="resultHandler(event)" />
<mx:TextArea id="test" x="10" y="10" width="452" height="348"/>
</mx:Application>

Hello Again Everybody,
I have found the answer to my problem. The Problem was that I had the wrong value assigned the variable "connString" insted of "Data Source=Family\SQLExpress;Initial Catalog=SDJames;User ID=sa;Password=Password1", it should have been "Data Source=Family\\SQLExpress;Initial Catalog=SDJames;User ID=sa;Password=Password1". Don't you just hate how just messing up with one character can mess up you entire application. Thanks to everybody who took time to look over my problem.
God Bless

Payload of SOAP-Message cannot be read

Hi,
I'm sending an easy message to the XI 3.0 soap-adapter:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
     <SOAP:Header/>
     <SOAP:Body>
          <plain>test</plain>
     </SOAP:Body>
</SOAP:Envelope>
Unfortunately I get always the error:
<SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
Thank you for reading und help,
Udo

Hi Stefan,
Yes, I go from Client to XI to R/3 via SOAP.
I don't know how the wsdl can solve my problem.
I use wfetch to send the message. I sent to
http://host:port/XISOAPAdapter/MessageServlet?channel=
:service:channel
as described in sap bibliothek.
Without the right namespace in the channel the receiver determination runs to an error but it works fine.
We are on XI 3.0 SP 9.
The error message coming from XI back to wfetch:
[code]<?xml version='1.0'?>\r\n
\r\n
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>\r\n
<SOAP:Body>\r\n
    <SOAP:Fault>\r\n
      <faultcode>SOAP:Server</faultcode>\r\n
      <faultstring>failed to call the adapter engine</faultstring>\r\n
      <detail>\r\n
        <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>\r\n
          <context>XIAdapter</context>\r\n
          <code>DeliveryException</code>\r\n
          <text><![CDATA[\r\n
com.sap.aii.af.mp.module.ModuleException\r\n
\tat com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:697)\r\n
\tat com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)\r\n
\tat com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:221)\r\n
\tat com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)\r\n
\tat com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:513)\r\n
\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:760)\r\n
\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:853)\r\n
\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)\r\n
\tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)\r\n
\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:339)\r\n
\tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:317)\r\n
\tat com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:810)\r\n
\tat com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)\r\n
\tat com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)\r\n
\tat com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)\r\n
\tat com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)\r\n
\tat com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)\r\n
\tat com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)\r\n
\tat java.security.AccessController.doPrivileged(Native Method)\r\n
\tat com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)\r\n
\tat com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)\r\n
Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception used by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:\r\n
\tat com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:122)\r\n
\tat com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)\r\n
\tat com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)\r\n
\tat com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:576)\r\n
\t... 20 more\r\n
Caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:\r\n
\tat com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:366)\r\n
\tat com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:123)\r\n
\tat com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:419)\r\n
\tat com.sap.engine.frame.core.thread.Task.run(Task.java:60)\r\n
\tat com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)\r\n
\tat com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)\r\n
          ]]></text>\r\n
        </s:SystemError>\r\n
      </detail>\r\n
    </SOAP:Fault>\r\n
</SOAP:Body>\r\n
</SOAP:Envelope>\r\n
[/code]
Regards (and thanks for your help), Udo

Weird soap issue: Cannot find the dispatch method

Hi,
I'm having strange problem with SOAP message.
I created a simple web service using jax-ws, wsgen, and so on. I deployed it on sun app server 9.0. I wrote client application (i'm using SAAJ 1.3) for testing. The response I'm getting is something like this:
<soapenv:Envelope xmlns:ns1="http://put/"
   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Client</faultcode>
         <faultstring>Cannot find the dispatch method</faultstring>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>First I thought there's a problem with webservice I created. So I downloaded soapui (www.soapui.org) for testing. I provided it with wsdl and endpoint. And web sevice seems to work corectly - response I got back was ok.
The strange part is: soap messages sent from soapui and from client application written by me seem to be identical. Both look like this:
<SOAP-ENV:Envelope
   xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:put="http://put">
   <SOAP-ENV:Body>
      <put:sayHello>
         <arg0>test</arg0>
      </put:sayHello>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>I even sniffed packets (WinDump) sent to application server and in both cases soap message is the same. There's only a slight difference in http headers. Here's what server log contains after receiving a soap message from my client application:
DetailsTimestamp:     2006-09-14 13:28:03.315
Log Level:      SEVERE
Logger:     javax.enterprise.resource.webservices.jaxws.server.soapmd
Name-Value Pairs:     _ThreadID=13;
Record Number:     443
Message ID:     Error in decoding SOAP Message Error in decoding SOAP Message at com.sun.xml.ws.encoding.
soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java
Complete Message
86)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.
toMessageInfo(SOAPMessageDispatcher.java:168)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.
invoke(SOAPMessageDispatcher.java:533)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:144)
     at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
     at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.handle(WSServletDelegate.java:279)
     at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:232)
     at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:77)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:189)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:371)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:264)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:281)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83)
Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:662)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:151)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:335)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:325)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:248)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:78)
     ... 39 moreI'm new to web services and I'm completely out of ideas what is the problem. I googled a lot but I can't find any solution. Any help would be appreciated :)
null

Are you saying I can't just write jax-ws based web service using @WebService and @WebMethod and then, on client side, write code like this?
SOAPConnectionFactory soapConnectionFactory = SOAPConnectionFactory.newInstance();
SOAPConnection connection = soapConnectionFactory.createConnection();
MessageFactory factory = MessageFactory.newInstance(SOAPConstants.SOAP_1_1_PROTOCOL);
SOAPMessage request = factory.createMessage();
// create proper message elements
URL endpoint = new URL(endpoint_url);
SOAPMessage response = connection.call(request, endpoint);
// process response
//

Error when calling SOAP Runtime functions

Hi Guys,
I have a requirement in which i have to consume a webservice and get a response from it but when i consumed the web service and tried to test it i got the below error please let me know solution for this as it is very urgent and also i am very new to web services stuff
Error when calling SOAP Runtime functions: SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")
Thanks
shivraj

Hi,
Have a look at this blog from Michal Krawczyk to find a solution:
The specified item was not found.
Hope this helps,
Grzegorz

Soap fault, cannot find the dispatch method

I deploy the HelloService example from "The Java EE 5 Tutorial
For Sun Java System Application Server Platform Edition 9, chapter 1" to Sun Java System Application Server Platform Edition 9.0 Beta (build b32g), I tested it and it works find but when I invoked it from Servicemix-3.0 which use org.apache.servicemix.components.saaj.SaajBinding i got the following response:
<?xml version="1.0" ?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://endpoint.helloservice/"><soapenv:Body><soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>soapenv:Client</faultcode><faultstring>Cannot find the dispatch method</faultstring></soapenv:Fault></soapenv:Body></soapenv:Envelope>
Using the Monitor to look at the request message I could not see any significant difference, follows both requests:
Test:
<?xml version="1.0" ?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://endpoint.helloservice/"><soapenv:Body><ns1:sayHello><arg0>ffg</arg0></ns1:sayHello></soapenv:Body></soapenv:Envelope>
servicemix:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Envelope xmlns:ns1="http://endpoint.helloservice/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <ns1:sayHello> <arg0>Leopoldo</arg0> </ns1:sayHello> </SOAP-ENV:Body> </SOAP-ENV:Envelope></SOAP-ENV:Body></SOAP-ENV:Envelope>
The log entry detail asociate is:
Message ID: Error in decoding SOAP Message Error in decoding SOAP Message at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java
Complete Message
86)     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.toMessageInfo(SOAPMessageDispatcher.java:168)     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.invoke(SOAPMessageDispatcher.java:533)     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:144)     at com.sun.xml.ws.server.Tie.handle(Tie.java:88)     at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:174)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:822)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:585)     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:262)     at java.security.AccessController.doPrivileged(Native Method)     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:295)     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:178)     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:390)     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:174)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:223)     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:664)     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:571)     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:846)     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:345)     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:237)     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:240)     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method     at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:662)     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:151)     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:335)     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:325)     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:248)     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:78)     ... 40 more
I shall appreciate any help on this issue

Any luck? I'm having the same problem with the HelloService deployed on AS9. The service tests ok and the client code in the jwsdk2.0 runs ok. When I attempt to access the service using axis 1.4, the same error occurs. I'll keep working on it, and post a solution if/when this is resolved.
Client code:
* Copyright 2001-2004 The Apache Software Foundation.
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*      http://www.apache.org/licenses/LICENSE-2.0
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import javax.xml.namespace.QName;
public class TestClient
   public static void main(String [] args) {
       try {
           String endpoint =
                    "http://localhost:9090/helloservice/HelloService";
           Service service = new Service();
           Call     call    = (Call) service.createCall();
           call.setTargetEndpointAddress( new java.net.URL(endpoint) );
           call.setOperationName(new QName("http://soapinterop.org/", "sayHello") );
           // Call to addParameter/setReturnType as described in user-guide.html
           //call.addParameter("testParam",
           //                  org.apache.axis.Constants.XSD_STRING,
           //                  javax.xml.rpc.ParameterMode.IN);
           //call.setReturnType(org.apache.axis.Constants.XSD_STRING);
           String ret = (String) call.invoke( new Object[] { "Hello!" } );
           System.out.println("Sent 'Hello!', got '" + ret + "'");
       } catch (Exception e) {
           e.printStackTrace();
}Error in decoding SOAP Message Error in decoding SOAP Message at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java
89)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.toMessageInfo(SOAPMessageDispatcher.java:187)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher$SoapInvoker.invoke(SOAPMessageDispatcher.java:571)
     at com.sun.xml.ws.protocol.soap.server.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:145)
     at com.sun.xml.ws.server.Tie.handle(Tie.java:88)
     at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:191)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot find the dispatch method
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.raiseFault(SOAPDecoder.java:674)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.decodeDispatchMethod(SOAPXMLDecoder.java:152)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:337)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:327)
     at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:250)
     at com.sun.xml.ws.encoding.soap.server.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:81)
     ... 31 more
Mesage:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:sayHello soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soapinterop.org/"><ns1:arg0 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">Hello!</ns1:arg0></ns1:sayHello></soapenv:Body></soapenv:Envelope>

Error when calling SOAP Runtime functions - Please help!

Hi,
Very new to SAP. I just installed SAPNW7.0ABAPTrialSP12 (sandbox server, with default options) and setup the
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/db/7c623cf568896be10000000a11405a/content.htm">Flight Data</a>.
I wanted to invoke some of the Flight Data functions through SOAP. So I invoked the following URL:
http://localhost:8000/sap/bc/srt/rfc/sap/BAPI_FLIGHT_GETDETAIL?sap-client=000&wsdl=1.1
I get the following error:
The following error text was processed in the system NSP : Error when calling SOAP Runtime functions
The error occurred on the application server hs_NSP_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
      Method: HANDLE_REQUEST of program CL_SOAP_TRANSPORT_EXTENSN_ROOTCP
      Method: HANDLE_REQUEST of program CL_SOAP_HTTP_EXTENSION========CP
      Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_SOAP_HTTP_EXTENSION========CP
      Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
      Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
      Module: %_HTTP_START of program SAPMHTTP
FROM Runtime Error Log:
Runtime Errors                     UNCAUGHT_EXCEPTION
Exception                          CX_SOAP_CORE
     Termination occurred in the ABAP program "CL_SOAP_TRANSPORT_EXTENSN_ROOTCP" -
           in "HANDLE_REQUEST".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 37
          of the (Include) program "CL_SOAP_TRANSPORT_EXTENSN_ROOTCM004".
Does anyone have any ideas on what is going on? Thanks in advance.

Hi,
Have a look at this blog from Michal Krawczyk to find a solution:
The specified item was not found.
Hope this helps,
Grzegorz

SAP WebAS SOAP runtime cannot recognize empty soap:Header /soap:Header

Similar Messages

Maybe you are looking for