Java Web Service error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog

Question 1

I encountered this error and found that it appeared to be due to using a URL that returned an HTTP 302 redirect instead of the WSDL directly.

The URL I was using was in the format /Service?wsdl, which redirected to a URL in the format /Service/wsdl/Service.wsdl. Once I used the redirect target URL directly, everything worked.

Question 2

I remember reading that it could be related to the endpoint expecting a trailing '/'. I'm not sure if this valid, but please try it and post here it if works.

Question 3

I had a similar error and when I checked the server logs - it was related to http server having encountered an unsupported http method in request. Due to this teh server returns an HTTP response that the SOAP client cannot handle ... hence Unexpected EOF in prolog Below is a snippet my web-server log for tomcat "localhost.XXXX.log"

org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [/services/*] only the HTTP methods [POST GET] are covered. All other methods are uncovered.

This gave following error on client side

 com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog

In my case since I was downgrading a secured service to unsecured and my web.xml had following stray entry that was restricting GET and post with a security constraint and I wasnt sending needed security parameters in the request..

<security-constraint>
    <web-resource-collection>
      <web-resource-name>restricted web services</web-resource-name>
          <url-pattern>/services/*</url-pattern>
          <http-method>GET</http-method>
          <http-method>POST</http-method>
        </web-resource-collection>

I removed this constraint to get rid of this error :-)

In your case it may not related to security constraint - but for sure its related to server sending raw http response - Please check your server/ client configuration and ensure it sends appropriate http request that are liked by http server

Question 4

I had a similar error and when I checked the server logs - it was related to http server having encountered an unsupported http method in request returns an HTTP response that the SOAP client cannot handle ... check your web-server logs

Question 5

Surely this isn't due to character or format issue. It's possible that the server didn't return any data, of which the Woodstox (wstx) was trying to parse into XML and failed, which resulted to this error.

Question 6

I had similiar issue and i have resolved with debugging. When i try to download WSDL in runtime i found that i could not get the WSDL because of the proxy. Please check that you can access the WSDL in runtime like this code:

  try {
      String wsdl = org.apache.commons.io.IOUtils.toString(new URL("http://YOUR_WSDL_URL"));
      System.out.println("WSDL => "+wsdl);
  } catch (IOException e) {
         e.printStackTrace();
  }

Question 7

One of the imports are missing. Please check routes to your xsd's.

Question 8

I had the same problem. I had to use the full path to the WSDL file to make it works.

Question 9

My contribution to this error is this:

I don't get this error when I am in debugging mode.

It seems that when the executor of the Java program that queries the WSDL Service (Java in my case) has the time to perform many requests, like in debugging mode, because of when sometimes the programs stops because I put some breakpoints, in this case I don't get this error.

When I run the program in production mode, yes.

But the requests are the same, the WSDL doesn't change, as well ad the endpoints.

It's like a limitation of the web Server, I think.