No, I'm pretty sure this is a problem in the generated client. When I
used tcpmon, I couldn't get the error at all. I don't get the error when
calling the web service from SoapUI, nor from the Eclipse Web Services
Test explorer.

 

I wrote a standalone Java program using the generated client stub to
call the web service 10 times. It fails every second call, i.e. 5 out of
the 10 calls fail, every time I run the program.

 

I'm pretty sure I didn't specify broken="true" when I generated the
client:

 

    <taskdef name="wsdl2java"
classname="org.apache.axis2.tool.ant.AntCodegenTask">

        <classpath>

            <fileset dir="${axis2-lib}" includes="*.jar"/>

        </classpath>

    </taskdef>

    <target name="gen-wsdl-client-sch">

        <wsdl2java wsdlfilename="ScheduleService.wsdl"
packagename="nz.co.datacom.foo" databindingname="jibx" synconly="true"
serverside="false" generateservicexml="false" unwrap="false"
targetsourcefolderlocation="../Client/src" overwrite="true">

            <parameter name="bindingfile" value="binding.xml"/>

        </wsdl2java>

    </target>

 

I'm just using the client stub generated by wsdl2java unchanged.

 

From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] 
Sent: Thursday, 11 February 2010 6:11 p.m.
To: axis-user@ws.apache.org
Subject: Re: com.ctc.wstx.exc.WstxEOFException

 

 

On Thu, Feb 11, 2010 at 2:26 AM, Colin Sharples [DATACOM]
<colin.sharp...@datacom.co.nz> wrote:

I have an Axis2 web service that was working fine, but in the last
couple of days has started misbehaving. Every now and then, the client
gets a com.ctc.wstx.exc.WstxEOFException when calling
OperationClient.execute().  The exception detail says: "Unexpected EOF
in prolog at [row,col {unknown-source}]: [1,0]"

 

The stack trace showed the fault occurred in
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(),
just after AxisEngine.receive().

 

I put some debugging into my service class, and it is clear that the
incoming request never gets into the service, which suggests that it is
the request from the client that is faulty. 


I think it gets this exception when it try to parse the response. see
the response message. You can use tcpmon[1] for that.

thanks,
Amila.

[1] http://ws.apache.org/commons/tcpmon/download.cgi 

         

        Does anyone have any idea what might be causing this?

         

        Colin Sharples

         

        Solutions Architect | Datacom Systems & Integration

        Email: colin.sharp...@datacom.co.nz | Mob: +64-27-457-6628

         




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Reply via email to