JWSDP 2.0 and SAAJ SOAP - envelope error

I've integrated JWSDP 2.0 SAAJ security into a J2EE servlet that sends and receives SAAJ SOAP. I have tested and verified all sample security configurations except encryptv1.xml and encryptv2.xml. My issues is that although I am able to encrypt messages within the servlet, I am unable to decrypt. I have a java client running on the command line that interacts with the servlet and it is able to encrypt and decrypt (actually decrypts the encrypted error response raised by the servlet). I am also able to get the client to interact (encrypt/decrypt) successfully with a simpler servlet on standalone tomcat. I am using jboss 4.0.3RC2 and jboss 4.0.4GA both with tomcat55 and java 5. The error I receive is as follows:
[STDOUT] ERROR: 'NOT_FOUND_ERR: An attempt is made to reference a node in a context where it does not exist.'
[STDOUT] Jun 5, 2006 12:16:13 PM com.sun.xml.messaging.saaj.soap.EnvelopeFactory createEnvelope
SEVERE: SAAJ0511: Unable to create envelope from given source
[STDOUT] Jun 5, 2006 12:16:13 PM com.sun.xml.wss.impl.SecurableSoapMessage findSoapHeader
SEVERE: WSS0369: Error getting SOAPHeader from SOAPEnvelope due to Unable to create envelope from given source:
[STDOUT] com.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.XWSSecurityException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to create envelope from given source:
[STDOUT] at com.sun.xml.wss.impl.misc.XWSSProcessor2_0Impl.verifyInboundMessage(XWSSProcessor2_0Impl.java:115)
Any help will be greatly appreciated...

I figured it out! I needed to remove the Timestamp in the server config file.
Thanks

Similar Messages

SOMETIMES - Could not load com.sun.xml.messaging.saaj.soap.Envelope

Hi there,
Well, it is mysterious - not to say frightning !
When I first start my tomcat I get an Exception like:; Could not load com.sun.xml.messaging.saaj.soap.Envelope
The second time it runs well. No Exception about classloading. And the app is nice.
Hmm, why ? Can�t find out.
I think that Exception has to have some relation to jars and where they are placed.
According to the JAXWS-page I placed:
jaxb-api.jar, jaxws-api.jar, jsr173_api.jar, saaj-api.jar
in my %JRE_HOME%\lib\endorsed\
so far so good !
The rest of the needed jars to run JAX-WS Webservices are in my WEB-INF/lib FOLDER
activation.jar and so on
Any Ideas ?
Here is the Exception I get when I invoke the Service
INFO: Illegal access: this web application instance has been stopped already. Could not load com.sun.xml.messaging.saaj.soap.Envelope. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1238)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.getSOAPPart(Message1_1Impl.java:78)
at com.sun.xml.ws.message.AbstractMessageImpl.readAsSOAPMessage(AbstractMessageImpl.java:177)
at com.sun.xml.ws.client.dispatch.SOAPMessageDispatch.toReturnValue(SOAPMessageDispatch.java:93)
at com.sun.xml.ws.client.dispatch.SOAPMessageDispatch.toReturnValue(SOAPMessageDispatch.java:57)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:188)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:192)
at idff.server.service.ArtifactResolver.resolve(ArtifactResolver.java:101)
at servlets.AssertionConsumerServlet.doPost(AssertionConsumerServlet.java:149)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:619)
09.08.2007 14:40:12 org.apache.catalina.core.StandardWrapperValve invoke
SCHWERWIEGEND: Servlet.service() for servlet AssertionConsumerServlet threw exception
java.lang.NoClassDefFoundError: com/sun/xml/messaging/saaj/soap/Envelope
at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.getSOAPPart(Message1_1Impl.java:78)
at com.sun.xml.ws.message.AbstractMessageImpl.readAsSOAPMessage(AbstractMessageImpl.java:177)
at com.sun.xml.ws.client.dispatch.SOAPMessageDispatch.toReturnValue(SOAPMessageDispatch.java:93)
at com.sun.xml.ws.client.dispatch.SOAPMessageDispatch.toReturnValue(SOAPMessageDispatch.java:57)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:188)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:192)
at idff.server.service.ArtifactResolver.resolve(ArtifactResolver.java:101)
at servlets.AssertionConsumerServlet.doPost(AssertionConsumerServlet.java:149)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:619)
Listening for transport dt_shmem at address: bundled_tomcat
Anybody help, please !

First, thanks for your reply jitu.
I don�t get this exception anymore.
Well, your hint was quite right, so I think I may give you the duke stars.
I found out that putting the jars into the shared/lib don�t work. Maybe it is because I am running 3 tomcat instances at the same time.
I put all the Jax-ws libs into the tomcat_home/common/lib directory.
And left the endorsed libs in the java endoresed directory.
putting the endorsed libs in the tomcat_home/common/lib/endorsed may also work.
regards and thanks,
footman

No SOAP Envelope error in SOAP Receiver Adapter

Hello Friends,
Informaiton:-
I have configured one Synchronous scenarion for SAP R/3 to PI 7.1 to Java based web applicaiton.
On the Receiver/Outbound side, i have configured the SOAP Receiver Adapter with the Target URL and SOAP Action.
Outbound and Inbound service interfaces have Request/Response and Fault messages.
Issue:-
While sending the Message, Below error is noticed in ABAP stack SXMB_MONI during the Call Adapter Stage and also in RWB (Channel Monitoring) .
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 {}RESPONSES; HTTP 200 OK
I also found that Request message is not reaching to the Java Web server.
I am taking the Same message Payload (found at Call Adapter Stage) and ussing it in XML Altova SPY Web client tool. There it is running scuccessfully and getting the Response message.
please suggest.
Thanks & Regards
Jagesh

Hi,
Yesterday i consumed the same WSDL file in Altova XML SPY and there it is working, getting the Response.
Now comparing the SOAP Request message reaching to the Third party Web server (which fall within the same Lane network)
from SAP PI and Altova XML SPY tool. I used TCP Gateway for the below scenarios.
(1)First i sent the SOAP message from PI and observed the RESPONSE message without the SOAP Envelope in TCP Gatway Trace and hence i am getting the No SOAP Envelope Error in PI.
(2)I consumed the same WSDLfile in Altova XML SPY and sent the SOAP message, here i got the Proper SOAP Response message and hence success in this case. (Used the same Data Payload as used in point 1)
(3)Now to identify the issue in the SOAP Request message being sent from PI, i used the same SOAP message sent in step 1 here, that means copy the entire SOAP ENvelope from the TCP gateway Trace and pasted it in Alota Spy and sent, there it is found running (got the response message from Third Party server).
One difference i found in HTTP Protocol statements in SOAP Request message in Point no 1 and Point no 2 above.
HTTP Protocols in Point 1 (Through PI).
POST HTTP/1.0
Accept: /
Host: 172.24.138.142:4544
User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
CallingType: SA
content-id: <soap-00306EEAC2051ED1839136CEE8564900 sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 1195
SOAPACTION: "Action1"
HTTP Protocols in Point 2 (Through Altova).
POST / HTTP/1.1
Content-Type: text/xml
User-Agent: XML Spy
SOAPAction: "Action1"
Host: 172.24.138.142:4544
Content-Length: 1195
Connection: Keep-Alive
Cache-Control: no-cache
Thanks to Mr. Stefan Grube for writting such a nice blog.
Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
Experts, please suggest me further.
Thansk & Regards
Jagesh

Generating SOAP Envelope when DO NOT USE ENVELOPE option is marked

My scenario: SPROXY => XI => 3rdParty WebService. Communication is synchronous. I've a problem with soap envelope. It is required by webservice, but when I use standard soap envelope generated by SAP I've a problem with receiving response from webservice.
So I want to create my own envelope. For this reason I've used DO NOT USE SOAP ENVELOPE option. Now the challenge comes. How can I create my own soap envelope?
Do you have any working example? Soap envelope should be added to message send from XI to 3rdParty WebService.
Helping answers => a lot of points

I'm talking about HTTP header.
When I'm sending SOAP request from SAP my whole message looks like when I use soap envelope
POST / HTTP/1.0
Accept: */*
Host: 192.168.132.179:54000
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Content-ID: <soap-02cce7702b1a11dd9902000c29ee261e[at]sap.com>
Content-Type: text/xml; charset=utf-8
Content-Disposition: attachment;filename="soap-02cce7702b1a11dd9902000c29ee261e[at]sap.com.xml"
Content-Description: SOAP
Content-Length: 259
SOAPACTION:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header/><SOAP:Body><ns0:Sd2Ids_SzfExport xmlns:ns0='http://www.dat.de/sdii/ids/Sd2SOAP.wsdl'><arg1>1234567899-0</arg1><arg2>1</arg2></ns0:Sd2Ids_SzfExport></SOAP:Body></SOAP:Envelope>
Always after such request I got and HTTP 411 error.
In opposite, when I'm sending request from e.g. Altova or SoapUI, my message looks:
POST / HTTP/1.1
Content-Type: text/xml; Charset=UTF-8
User-Agent: XML Spy
Host: 192.168.132.179:54000
Content-Length: 489
Connection: Keep-Alive
Cache-Control: no-cache
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body>
          <m:Sd2Ids_SzfExport xmlns:m="http://www.dat.de/sdii/ids/Sd2SOAP.wsdl">
               <arg1 xsi:type="xsd:string">1234567899-0</arg1>
               <arg2 xsi:type="xsd:string">1</arg2>
          </m:Sd2Ids_SzfExport>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
After that request WebService response is correct.
You can find such differences (except Content-length which is a result of XML message formatting) in those two headers:
- for first is used HTTP 1.0 protocol for later 1.1
- in SAP header an info about attachment is added
After a lot of test I thing that those attachment info in header of HTTP is causing a problem. So I want to use DO NOT USE SOAP ENVELOPE option to generate HTTP header without Content-Disposition and generate SOAP Envelope manually.

Problem in mapping while using Do not Use SOAP Envelope

Hi All,
This is wrt my thread 'Removing and adding SOAP Envelope'
I am currently working on SOAP-XI-Proxy Scenario.
For some un avoiadable reason, I had to use the option 'DO not use SOAP Envelope' .So the SOAP Envelope came withen the payload and in the pipeline, I can see the payload prefixed by '<?xml version="1.0" ?>' .
Now my payload looks like
<?xml version="1.0" ?> ( no more the encoding="utf-8" notation is there)
<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>
<Complaint_Request xmlns="urn:******createserviceticket">
<CaseNo>12345</CaseNo>
<CustomerNo>12345</CustomerNo>
</Complaint_Request>
</soapenv:Body>
</soapenv:Envelope>
To accomodate the change, I also changed my request structure as
<Complaint_Request> (My new message Type)
    <Envelope>
     <Body>
       <Complaint_Request> (My previous message Type)
        <caseNo>
        <CustomerNo>
But I am facing problem in mapping the values to the target structure (which is a flat structure),
as the payload doesnot start with ' ns1: ' notation any more . Even XSLT mapping is not working.
When I am pasting the payload in the Testing Mapping Editor, the Source Node are correctly
formed, but all come in RED . But as the root node , ie 'ns0' is not there, the value
from child nodes are not getting mapped to the target fields.
Regards,
Subhendu

Hi Joel,
SAP says, when we use the option 'DO Not Use SOAP Envelope', the payload also contains the SOAP
Envelope. So it is obvious that the payload wont start with 'ns0' notation.
So I am searching for a solution, when we use that option.
Regards,
Subhendu

Error with Do Not use SOAP envelope

All,
I used the do not send SOAP envelope option in the SOAP receiver adapter.
Instead of XSLT, I used JAVA mapping to create the entire SOAP message ( Am more comfortable with Java and this is just a trial) , and this is the output of my java mapping with the SOAP envelope created,
<i><?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2001/12/soap-envelope"soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding"><soap:Header></soap:Header><soap:Body><ns1:GetQuote xmlns:ns1="http://www.webserviceX.NET/"><ns1:symbol>SAP</ns1:symbol></ns1:GetQuote></soap:Body></soap:Envelope></i>
Am using the STOCK Quote for testing purposes and this is the error I am getting when testing my interface,
<i><faultstring>System.Web.Services.Protocols.SoapException: Server found request content type to be '', but expected 'text/xml'. at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() at System.Web.Services.Protocols.WebServiceHandler.Invoke() at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring></i>
Any directions / inputs on how to resolve this issue?
Regards,
Bhavesh

Henrique,
Tried various permutations~~ The only new error / progress seems to be for this,
SOAPAction "http://www.webserviceX.NET/GetQuote"
This is giving me an error ,
<i>HTTP server code 400 reason Bad Request explanation <h1>Bad Request (Invalid Header Name)</h1></i>
Also, tried by adding the Colon after SOAPAction,
SOAPAction: "http://www.webserviceX.NET/GetQuote"
Same error
Final thing i guess is to make SOAPAction all small as soapaction and check if it works. Will let you know.
Regards,
Bhavesh

'/soap:Envelope ' in extract throws invalid token error

I'm receiving xml via webservice/soap and placing in an XMLTYPE table. Upon trying to execute a test query:
SELECT
EXTRACTVALUE(VALUE(d),'Destinations/CountryID') AS ID
FROM X_TEST p,
TABLE (xmlsequence(EXTRACT(p.object_value,'/soap:Envelope/soap:Body/GetUserDestinationResponse/GetUserDestinationResult/DestinationResults/DestinationsList//Destinations'))) d
I get an error similar to: (note path here in error is diff than above extract statement)
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00601: Invalid token in: 'soap:Envelope/soap:Body/GetUserDestinationResponse/GetUserDestinationResult/DestinationResults/DestinationsList/Destinations/DestinationList/Destination//Provider'
Without the soap:Envelope/soap:Body there is no error. Is there a problem using the ':' here?
Here's a snippet of the stored xml:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<GetUserDestinationsResponse xmlns="http://xxx.xxx.xxx.xx/somesite_ws/">
<GetUserDestinationsResult>
<DestinationResults>
<DestinationsList>
<Destinations>
<CountryID>101</CountryID>
<CountryDescription>Indonesia</CountryDescription>
</Destinations>
</DestinationList>
</DestinationResults>
</GetUserDestinationsResult>
</GetUserDestinationsResponse>
</soap:Body>
</soap:Envelope>

Thanks,
that set me in the right direction - I had tried the third parm before but must not have been just right being that there are multiple namespaces given. Appears I have to always use the namespace parm to accurately obtain the data. To conclude - this is what I ended up with to get this returning data properly:
SELECT
EXTRACTVALUE(VALUE(d),'/Destination/DestinationId', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"') AS ID,
Get_Point(EXTRACTVALUE(VALUE(d),'/Destination/Longitude', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"'),
EXTRACTVALUE(VALUE(d),'/Destination/Latitude', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"')) AS geom,
EXTRACTVALUE(VALUE(p),'/Provider/ProviderName', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"') AS provider_name,
EXTRACTVALUE(VALUE(p),'/Provider/ProviderSpecific/HospitalInformation/whoAvainFlu', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"') AS avaianflu,
VALUE(p) AS xmlb
FROM X_MEDAIRE xml
,TABLE (xmlsequence(EXTRACT(xml.object_value,
'/soap:Envelope/soap:Body/*', 'xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"'
))) e
,TABLE (xmlsequence(EXTRACT(VALUE(e),
'/long/path/after/soap', 'xmlns="http://xxx.xxx.xxx.xx/some_ws/"' ))) d
,TABLE (xmlsequence(EXTRACT(VALUE(d),
'/Destination/ProviderList/Provider', 'xmlns="http://xxx.xxx.xxx.xxx/some_ws/"' ))) p
WHERE
EXTRACTVALUE(VALUE(p),'/Provider/ProviderType', 'xmlns="http://xxx.xxx.xxx.xxx/some_ws/"') = 'Hospital'

Web Service error: javax.xml.soap.SOAPException: Error parsing envelope:

Oracle Database 10g Enterprise Edition Release 10.2.0.1.0
dbws-callout-utility 10.1.3.1
JPublisher 10g Release 10.2
Generating command:
./jpub -u reklaam/pswd -proxywsdl=http://auster.mbp.ee:8082/Service.asmx?WSDL -endpoint=http://auster.mbp.ee:8082/Service.asmx -dir=tmp -plsqlpackage=adserver -omit_schema_names -proxyopts=jaxrpc,noload
loading:
loadjava -u reklaam/pswd -r -v -f -genmissing plsql_proxy.jar
executing script files and granting
dbms_java.grant_permission('REKLAAM', 'SYS:java.lang.RuntimePermission', 'accessClassInPackage.sun.util.calendar', '' );
dbms_java.grant_permission('REKLAAM', 'SYS:java.lang.RuntimePermission', 'getClassLoader', '' );
dbms_java.grant_permission('REKLAAM', 'SYS:java.net.SocketPermission', '*', 'connect,resolve' );
dbms_java.grant_permission('REKLAAM', 'SYS:java.util.PropertyPermission', '*', 'read,write' );
dbms_java.grant_permission( 'REKLAAM', 'SYS:java.lang.RuntimePermission', 'getClassLoader', '' );
Now when I execute ws procedure I got exception:
ORA-29532: Java call terminated by uncaught Java exception: java.rmi.RemoteException: java.rmi.RemoteException:Error parsing envelope: most likely due to an invalid SOAP message.; nested exception is:
javax.xml.soap.SOAPException: Error parsing envelope: most likely due to an invalid SOAP message.
ORA-06512: at "REKLAAM.ADSERVER", line 29
ORA-06512: at line 13
udump trace file:
java.rmi.RemoteException: java.rmi.RemoteException:Error parsing envelope: most likely due to an invalid SOAP message.; nested exception is:
javax.xml.soap.SOAPException: Error parsing envelope: most likely due to an invalid SOAP message.
at genproxy.runtime.ServiceSoap12_Stub.createClientFromObject(genproxy.runtime.ServiceSoap12_Stub:270)
at genproxy.ServiceSoap12Client.createClientFromObject(ServiceSoap12Client.java:40)
at genproxy.ServiceSoap12ClientJPub.createClientFromObject(ServiceSoap12ClientJPub.java:144)
What's wrong?

I have exactly the same issue, do anyone have some good suggestions ?

PHP5 SOAP WSDL and Xcelsius 2008 communication error

Hi,
I wood like to use PHP5 Soap server and WSDL for Xcelsius2008.
Now Xcelsius 2008 can read WSDL parameters, and data from Xcelsius appear in Soap server, but in the Soap Response is the error message:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
    <faultcode>SOAP-ENV:Client</faultcode>
    <faultstring>Bad Request</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
My WSDL is here:
http://www.tanit.hu/custimp/wsdl/hello/hello_04.wsdl
My PHP5 Soap Server:
<?php
ini_set("soap.wsdl_cache_enabled","0");
$server = new SoapServer("hello_04.wsdl");
class HelloService{
function doHello($yourName){
    if (strlen(trim($yourName))) {
      return "Hello ".$yourName;
    } else {
      throw new SoapFault("Server","The input parameter is Empty!");
?>
My PHP5 Soap Client (is working properly):
<?php
ini_set("soap.wsdl_cache_enabled","0");
try{
$sClient = new SoapClient('http://www.tanit.hu/custimp/wsdl/hello/hello_04.wsdl');
$response = $sClient->doHello('MyName');
echo $response;
} catch(SoapFault $e){
var_dump($e);
?>
Could somebody help me?
Thx.

OK.
[I found this.|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233343330333133373334%7D.do]

How to resolve error "No SOAP Envelope but 1 {} PARAMETERS"

Hi,
I have configured an interface where the sender (SAP system) sends out a message via proxy on the Local Integration Engine, which is after XI processing supposed to be posted via HTTP (using the SOAP Adapter).
The message is processed correctly by XI, but fails to pass the SOAP Comm Channel. The error message in the Communication Channel Monitoring reads:
SOAP: call failed: java.io.IOException:No SOAP Envelope but 1 {} PARAMETERS; HTTP 200 OK
Can anyone help me understand what this means and how I can resolve this? Thanks!

Dear Johannes,
Is the SOAP call taking place synchronously ? It looks like at the end of your SOAP channel, system is not responding as expected by XI (you seem to receive the regular HTTP 200 OK code, but it does not match SOAP protocol requirements) ...
I've had such issues when web services were down due to web server issue (in this case, you just get, for instance, HTTP 500 response body, which not really SOAP compliant)
Rgds
Chris

SOAP Envelope - HTTP_EXCEPTION - HTTP 500 Internal Server Error

Pessoal, o cliente em que estou utiliza uma solução para NFe que não é o GRC.
Para tentar solucionar o problema do SOAP 1.2 e do message header, estou tentando criar o SOAP Envelope utilizando um XSLT, e no Communication Channel eu estou flegando Do not use soap envelope e colocando os modules para os charset, assim como na nota da SAP.
O que está ocorrendo é que estou tendo o seguinte erro:
com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Conversei com um rapaz na SEFAZ e ele diz que não está chegando nada pra ele.
O SOAP Envelope que estou mandando é:
está dentro de tags CDATA.
Alguém saberia o que está ocorrendo?
Muito obrigao,
Leandro Rocha

Olá Henrique, muito obrigado pela rápida resposta.
O erro que dá no audit log é:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error. Setting message to status failed.
A mensagem que aparece no adapter é a padrão do SOAP Document:
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:wsse="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
- <SAP:Main versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
<SAP:TimeSent>2010-11-04T13:36:35Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="" scheme="" />
<SAP:Service>NFe_recepcao</SAP:Service>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SEFAZ_RS</SAP:Service>
</SAP:Receiver>
<SAP:Interface namespace="http://www.gerdau.com.br/nfe">NFe_recepcao_inbound_sync</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Diagnostic SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:HopList SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2010-11-04T13:36:39Z" wasRead="false">
<SAP:Engine type="PE" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">PE</SAP:Adapter>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2010-11-04T13:36:39Z" wasRead="false">
<SAP:Engine type="IS">is.00.ebsgerd26</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2010-11-04T13:36:41Z" wasRead="false">
<SAP:Engine type="AE">af.p7d.ebsgerd26</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>dfe81887-3f6a-55f1-b933-0050568169b4</SAP:MessageId>
</SAP:Hop>
</SAP:HopList>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:payload-DFE818873F6A21F1B9330050568169B4">
<sap:Name>MainDocument</sap:Name>
<sap:Description />
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Mais uma vez, muito obrigado,
Leandro

Avoid using Username and password in SOAP Envelope

Hi Team
I am working on calling the sercured web-service from PLSQL and able to call it successfully and get the response.
In the SOAP envelope, I have header and body.
Header contains the WS Security which includes username and password to authenticate the web-service and body contains the actual input pay load for service.
Currently, header has username and password as 'hard-coded', is there a way to avoid the usage of username and password.
We already tried to SIF for EBS methodology where in following steps are done:
1) Create and event in EBS.
2) Pass the event along with payload to SOA.
3) SOA receives the event and triggers web-service and gets the response.
4) Pass the response to EBS.
This technique does avoid usage of username and password but takes 20 seconds to do the job. However, the appraoch above takes hardly 1 second.
Please let me know in case any one has any idea on how to avoid credentials usage in SOAP envelope.
Thanks
Mirza Tanzeel

How about doing away with that approach entirely?
Password authentication requires one to keep a secret, secret. And that is the primary problem as how does one safely guard the secret, and manage the secret (by regularly changing)?
Relying on secrets is a problem. I have never been a fan of password based security.
Instead:
a) use HTTPS to secure communication between sender and receiver
b) use robust firewall rules to ensure that only sender is allowed to communicate with receiver
c) implement sound network management and exception reporting (to detect and prevent violations on network infrastructure level)
If you lack in the network infrastructure and administration areas, then:
a) make the web service endpoint on server on localhost only (do not expose it to the outside world)
b) establish a trusted ssh connection between sender and receiver using strongly encrypted RSA/DSA keys
c) configure sender with a service that opens a reverse tunnel to target, exposing the web service as a local port on its localhost

Duplicate soap envelope with JRockit and not Sun JDK

I have been installed Weblogic 10.3.6 with Sun JDK 1.6 on Windows 7 64 bit. This has worked great for a client sending in a soap request which is processed in my war as a 1.2 message. Debugging this shows the response is valid in my code, and works on Sun 1.6 fine.
When I switched to JRockit [jrockit-jdk1.6.0_33-R28.2.4-4.1.0-windows-x64] I started to receive a duplicate soap envelope and soap body wrapped around the valid soap envelope which worked before.
With the only change being switching to JRockit, this must be the cause of the addition of the duplicate the soap body and envelope. I searched this forum and Google and have not found a reason or solution.
Any ideas on a solution?

Seems to be the case that using MTOM stops this problem with JRockit. Strange but apparently true (so far).

No serializer found for class com.sun.xml.messaging.saaj.soap.ver1_1.Messag

Hi,
I am developing a soap web service using apache axis tool. I am using tomcat6 and jdk6. I need to return SOAPMessage as return object from remote interface methods. Now I have success fully deploy web service in tomcat. Also I have create client too, but when I am trying to call web service throw client then it show me a exception on client is
org.xml.sax.SAXParseException: Premature end of file.
and on server log, it show me this exception
java.io.IOException:
xisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.io.IOException: No serializer found for class com.sun.xml.messaging.saaj.soap.ver1_1.M
ssage1_1Impl in registry org.apache.axis.encoding.TypeMappingDelegate@98062f
faultActor:
faultNode:
faultDetail:
       {http://xml.apache.org/axis/}stackTrace:java.io.IOException: No serializer found for class com.su
.xml.messaging.saaj.soap.ver1_1.Message1_1Impl in registry org.apache.axis.encoding.TypeMappingDelegate@
8062f
       at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1507)
       at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
       at org.apache.axis.encoding.SerializationContext.outputMultiRefs(SerializationContext.java:1055)
       at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:145)
       at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
       at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
       at org.apache.axis.Message.writeTo(Message.java:539)
       at org.apache.axis.transport.http.AxisServlet.sendResponse(AxisServlet.java:902)
       at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:777)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
       at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:2
0)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:58
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
       at java.lang.Thread.run(Thread.java:619)
       {http://xml.apache.org/axis/}hostname:EMRG-409964-L19
ava.io.IOException: No serializer found for class com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
n registry org.apache.axis.encoding.TypeMappingDelegate@98062f
       at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:317)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
       at org.apache.axis.Message.writeTo(Message.java:539)
       at org.apache.axis.transport.http.AxisServlet.sendResponse(AxisServlet.java:902)
       at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:777)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
       at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:2
0)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:58
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
       at java.lang.Thread.run(Thread.java:619)
aused by: java.io.IOException: No serializer found for class com.sun.xml.messaging.saaj.soap.ver1_1.Mess
ge1_1Impl in registry org.apache.axis.encoding.TypeMappingDelegate@98062f
       at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1507)
       at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
       at org.apache.axis.encoding.SerializationContext.outputMultiRefs(SerializationContext.java:1055)
       at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:145)
       at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
       at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
       ... 19 moreI have deploy new version of saa-impl.jar and saaj-api.jar too. And I also have deploy webservice-rt.jar too in server lib and application lib folder. but still this exception is there. I dont understand, how can I over come from this error. If some one have resolved this type of exception then please reply. Please reply me on [email protected]
--Thanks in Advance
Umashankar Adha
Sr. Soft. Eng.
United States

FYI, now I'm in work:
import javax.xml.namespace.*;
import javax.xml.rpc.*;
import javax.activation.*;
import javax.mail.*;
import com.sun.xml.messaging.saaj.*;
-classpath D:\jwsdp-1.3\jaxp\lib\endorsed\dom.jar;D:\jwsdp-1.3\jaxp\lib\endorsed\xercesImpl.jar;D:\jwsdp-1.3\saaj\lib\saaj-impl.jar;D:\jwsdp-1.3\saaj\lib\saaj-api.jar;D:\jwsdp-1.3\jwsdp-shared\lib\activation.jar;D:\jwsdp-1.3\jwsdp-shared\lib\mail.jar;D:\jwsdp-1.3\jaxrpc\lib\jaxrpc-api.jar;D:\jwsdp-1.3\jaxrpc\lib\jaxrpc-impl.jar;D:\jwsdp-1.3\jaxrpc\lib\jaxrpc-spi.jar;D:\jwsdp-1.3\jwsdp-shared\lib\jax-qname.jar
Those are what I had to use to get it working.
Chris

Receiver SOAP Adapter error

Hi All,
         I am getting this response error message in my receiver SOAP Adapter while invoking a synchronous webservice.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <ProcessMessageResponse xmlns="http://Sleek.Integrator.Messaging" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProcessMessageResult>Value cannot be null. Parameter name: Request string is a null reference.</ProcessMessageResult>
</ProcessMessageResponse>
Thx in advance
Ravijeet

Hi All,
         I am still getting the same error value is null. I am not able to track what could be the cause of the error. If I am taking the message from SXMB_MONI and using it in a client tool it is successfully calling the webservice.
Do we need to explicitly mention in some configuration that content type is soap/xml. SOAP header is omitting the content type or is not specifying "soap/xml" as the content type.
I am interacting with a WAF websevice, is there any compatibilty issue with Windows Webservice and SAP XI?
Also what should I pick as the SOAP Action from this wsdl file definition
<wsdl:portType name="IMessageProcessor">
          <wsdl:operation name="ProcessMessage">
               <wsdl:input message="tns:IMessageProcessor_ProcessMessage_InputMessage" wsaw:Action="XXX.Messaging/ProcessMessage"/>
               <wsdl:output message="tns:IMessageProcessor_ProcessMessage_OutputMessage" wsaw:Action="XXX.Messaging/ProcessMessageResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:service name="MessageProcessor">
          <wsdl:port name="BasicHttpBinding_IMessageProcessor" binding="i0:BasicHttpBinding_IMessageProcessor">
               <soap:address location="http://XXX.com/cardax/provisioningservice"/>
          </wsdl:port>
Thx in advance
Ravijeet

JWSDP 2.0 and SAAJ SOAP - envelope error

Similar Messages

Maybe you are looking for