Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
3 replies Latest Post - ‏2014-02-01T19:04:58Z by HermannSW
rdp87
rdp87
40 Posts
ACCEPTED ANSWER

Pinned topic Incomplete markup or missing document element at line 1 of http://ip:port/uri

‏2014-01-02T10:44:41Z |

Hi All,

I am seeing incomplete markup error in web service proxy and not able to trace the error. Response coming from back-end server is soap message and this error is occurring intermittently like in 100 requests 2 or 3 are failing. 

Please help if there is any option to trace the error. Any help regarding this will be much appreciated.

Thanks & Happy new year...

  • kenhygh
    kenhygh
    1467 Posts
    ACCEPTED ANSWER

    Re: Incomplete markup or missing document element at line 1 of http://ip:port/uri

    ‏2014-01-02T12:47:08Z  in response to rdp87

    Happy new year to you!

    I'd try to narrow down the failure scenario. Is there something in the backend server logs that would help? This is often the result of a failure in the backend server that's producing an error message in HTML rather than SOAP.

    To see the offending response, the best way to see exactly what's happening is a packet capture. However, this can be really hard to do, especially if your failures are only occurring in Production.

    Another method that I've used is to create a Non-XML MultiProtocol Gateway, have your WSP route through the MPGW, and capture the failure in a probe (or log). However, this assumes you can recreate the failure in a non-Prod environment.

  • haranath
    haranath
    37 Posts
    ACCEPTED ANSWER

    Re: Incomplete markup or missing document element at line 1 of http://ip:port/uri

    ‏2014-01-31T19:51:01Z  in response to rdp87

     As you mentioned that service type is webservice proxy, I guess it's request & response types are soap messages.  If the backend server of WSP returns an invalid soap message then you will get the error("incomplete markup etc"). if possible try to execute the backend server through soap UI or some other tool   you will be able to figure out the problem. Some times  special characters in response makes the soap  message  invalid.

     

    For example, if your backend server is Webspehere application server and it is down then  it returns HTML as response instead of SOAP.