[ISS.0088.9125] SOAP request does not conform to the SOAP message model

, ,
1

Hi,

I have a wmusers certificated web service ( WSDL - Document / Literal SOAP-MSG Example by cjeganathan ) exposed on my IS 6.5 SP2. When I try to invoke them by a client (in my case EJB3 wsclient on jboss) I get this error code: [ISS.0088.9125] SOAP request does not conform to the SOAP message model.

This is the soap request that I send with my client (catch(log) on the application server):

<?xml version='1.0' encoding='UTF-8'?>
<env:Envelope 
xmlns:enc='http://schemas.xmlsoap.org/soap/encoding/' 
xmlns:env='http://schemas.xmlsoap.org/soap/envelope/' 
xmlns:xsd='http://www.w3.org/2001/XMLSchema' 
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<env:Header></env:Header>
<env:Body>
<ns2:Hello xmlns:ns2="hello.com"><inputString>Pirola</inputString></ns2:Hello>
</env:Body>
</env:Envelope>

This is the SOAP request that I find in HelloTest flow service created by cjeganathan:

<?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/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<nsp:Hello xmlns:nsp="hello.com">
  <inputString>World!</inputString>
</nsp:Hello></SOAP-ENV:Body>
</SOAP-ENV:Envelope>

In my opinion the two request are the same!

This is the SOAP Fault that webMethods return to me:

<SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
 <SOAP-ENV:Body>
  <SOAP-ENV:Fault xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'>
   <faultcode>SOAP-ENV:Client</faultcode>
   <faultstring>[ISS.0088.9125] SOAP request does not conform to the SOAP message model</faultstring>
   <faultactor>http://habanero:5555/soap/default</faultactor>
   <detail xmlns:webM='http://www.webMethods.com/2001/10/soap/encoding'>
    <webM:validationError>
     <webM:pathName xmlns:webM='http://www.webMethods.com/2001/10/soap/encoding'>/</webM:pathName>
     <webM:errorCode xmlns:webM='http://www.webMethods.com/2001/10/soap/encoding'>NV-002</webM:errorCode>
     <webM:errorMessage xml:lang='i-default' xmlns:webM='http://www.webMethods.com/2001/10/soap/encoding'>[ISC.0082.9002] Unable to retrieve root element</webM:errorMessage>
    </webM:validationError>
   </detail>
  </SOAP-ENV:Fault>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Can you help me?
Somebody know what type of problem I have in my request?
Some body know how to catch(log) the SOAP request on webMethods IS? (the previous request was catched on application server)
I try with another client implementation (Axis2) but I have the same error code!

2

Can you pass me the service code by mail (mrzezino@wp.pl) ?

3

Hi,

Thanks for email. Now I know a little bit better what is going on.
The first request at the webMethods service is translate into IData struncture:

HelloRequest (root document)
→ ns2:Hello (sub document)
----> inputString (field)

And then we’ve got field name: HelloRequest/ns2:Hello/inputString

At the second request you’ve got structure:
HelloRequest/nsp:Hello/inputString

Please look carefully on the namespace. At first request you’ve got ns2, and on the second one you’ve got nsp. This is probably the reason of this error :wink:

Regards,
Konki

4

You should also try this:

Workaround\resolution:

Added in these server extended settings:

  1. watt.server.SoapRPC.debug=true

(dumps the outbound message and incoming soap:Body to the console, nohup file)

  1. watt.server.SoapRPC.verbose=true

(dumps the pipeline used to create the out bound message to the console, nohup file)

Restart the IS. If still cannot display the SOAP messages in server log, then you may need third party network sniffer tool to capture the inbound SOAP traffic to your WS listener:

E.g.

  1. tcpmon ([url]http://ws.apache.org/commons/tcpmon/[/url])
  2. paros ([url]http://www.parosproxy.org/functions.shtml[/url])
  3. Apache Jmeter ([url]http://jakarta.apache.org/jmeter/[/url])
  4. soapUI - [url]http://www.soapui.org/[/url] – best tool

HTH,
RMG

5

Konki…It’s a good catch and i did noticed the same after.