[ISS.0088.9135] A WMDocument Exception while calling pub client http

, ,
1

i m able to get the resonse successfully in SOAPUI.but if i try to ivoke the same webeservice URL in pub client http service getting the below error

[ISS.0088.9135] A WMDocument Exception was thrown in the server, usually because an XML block was not well-formed

any one pls help

2

What is your IS version on?

Please check the below article and resolution:

Consumer webservice:
In 8.2 we get a weird error like below:

[ISS.0088.9135] A WMDocument Exception was thrown in the server, usually because an XML block was not well-formed.

Resolution:

Customer installed the latest fix and it resolved the issue.

IS_8.2_SP2_Core_Fix8

Other resolution is re-generate the web service connector and try it:

HTH,
RMG

3

we are using the IS version 7.1.2.pls help the wellformed xml format appliable for this version

4

Hi,

[ISS.0088.9135] A WMDocument Exception was thrown in the server, usually because an XML block was not well-formed

Check if your XML block is well formed.

Have a look at the webMethods Integration Server 7.X Readme or webMethods Integration Server 8.X SP2 Readme And then we can try installing the fix level if required.

5

Can you try

Other resolution is re-generate the web service connector and should resolve?

HTH,
RMG

6

actually the problem here is with the wsdl URL i given

i just copied and pasted the WSDL url from the provider/consumer properties

to pub client http like below

http://SAKTHI-PC:5555/ws/Default:Provider1?WSDL

but the error in webMethods returning is wmDocument exception,xml is not welformed
so i m only focusing on the error and also input xml may be wrong

i just changed the wsdl URL to below
http://SAKTHI-PC:5555/ws/Default:Provider1

i am able to get the soap response now.thanks guys for your support

7

OK make sense now with the URL correction as I Initially thought the culprit

HTH,
RMG

8

:slight_smile: Thanks for updating us back.

9

The two types of the URL mentioned by Sakthi have different purposes:

The URL ending with “?WSDL” is for retrieving the WSDL from IS, which can be used by consumer to generate service from it (as SoapUI do).

The URL without “?WSDL” is used to call the WebService on IS (SoapUI handles this upon generating the request sample from the WSDL).

Regards,
Holger

10

I’m facing the same issue. I tried recreating the connector(provider) but no help…

Details -

I’m exposing a webService provider. When customer calls this provider service, they are getting below error -

<SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema (http://www.w3.org/2001/XMLSchema)" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance (http://www.w3.org/2001/XMLSchema-instance)" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ (http://schemas.xmlsoap.org/soap/envelope/)">
  <SOAP-ENV:Header/><SOAP-ENV:Body>
   <SOAP-ENV:Fault>
    <faultcode>SOAP-ENV:Client</faultcode>
    <faultstring>[ISS.0088.9134] Exception occurred while processing the body of the message</faultstring>
    <faultactor>https://<server>:<port>/ws/folder:service (https://<server>:<port>/ws/folder:service)</faultactor>
    <detail>[ISS.0088.9135] A WMDocument Exception was thrown in the server, usually because an XML block was not well-formed</detail>
   </SOAP-ENV:Fault>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
11

What do you see in the IS logs during this error occurs or SOAP request in your service pipeline?

HTHm
RMG

12

you are right. Issue is with the request.

For fellow members my
debugging steps -

  1. As the error is occurring before the request enters into the service, i managed to get the same request over mail.

  2. To my surprise it is just the xml without the soap framework. (Http call with only xml). Hmmm… That’s against the requirement.

  3. To confirm the source of error, I have passed this request to wmpublic service ‘stringToSOAPdata’. I got the same error.

  4. Now asked my customer to wrap this xml in the soap body and also to add the soap headers.

  5. Now it’s all good!!

Thanks

13

Glad to hear issue resolved as expected: