You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Colin Sharples [DATACOM]" <Co...@datacom.co.nz> on 2010/02/10 21:56:22 UTC

com.ctc.wstx.exc.WstxEOFException

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. 

 

Does anyone have any idea what might be causing this?

 

Colin Sharples

 

Solutions Architect | Datacom Systems & Integration

Email: Colin.Sharples@datacom.co.nz | Mob: +64-27-457-6628

RE: com.ctc.wstx.exc.WstxEOFException

Posted by "Colin Sharples [DATACOM]" <Co...@datacom.co.nz>.
Not easily, as it is commercially confidential.

 

It seems to have resolved itself now. I had renamed a field in one of the domain objects, but the schema in the WSDL was still referring to the old field name. I changed the schema to use the correct field name, and now the generated client works every time.

 

What I want to know now is, why did it work at all!! How did it manage to return the correct result some of the time, but not all the time? Weird.

 

Thanks anyway.

 

From: Martin Gainty [mailto:mgainty@hotmail.com] 
Sent: Friday, 12 February 2010 4:09 p.m.
To: axis-user@ws.apache.org
Subject: RE: com.ctc.wstx.exc.WstxEOFException

 

can you publish the wsdl and the accompanying xsds?

Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.







________________________________

Subject: RE: com.ctc.wstx.exc.WstxEOFException
Date: Fri, 12 Feb 2010 15:47:49 +1300
From: Colin.Sharples@datacom.co.nz
To: axis-user@ws.apache.org

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:amilasuriarachchi@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] <Co...@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.Sharples@datacom.co.nz | Mob: +64-27-457-6628

	 




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

 

________________________________

Hotmail: Powerful Free email with security by Microsoft. Get it now. <http://clk.atdmt.com/GBL/go/201469230/direct/01/>

RE: com.ctc.wstx.exc.WstxEOFException

Posted by Martin Gainty <mg...@hotmail.com>.
can you publish the wsdl and the accompanying xsds?

Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.




Subject: RE: com.ctc.wstx.exc.WstxEOFException
Date: Fri, 12 Feb 2010 15:47:49 +1300
From: Colin.Sharples@datacom.co.nz
To: axis-user@ws.apache.org
















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:amilasuriarachchi@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]
<Co...@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.Sharples@datacom.co.nz
| Mob: +64-27-457-6628

 














-- 

Amila Suriarachchi

WSO2 Inc.

blog: http://amilachinthaka.blogspot.com/

 		 	   		  
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
http://clk.atdmt.com/GBL/go/201469230/direct/01/

RE: com.ctc.wstx.exc.WstxEOFException

Posted by "Colin Sharples [DATACOM]" <Co...@datacom.co.nz>.
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:amilasuriarachchi@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]
<Co...@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.Sharples@datacom.co.nz | Mob: +64-27-457-6628

	 




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

Re: com.ctc.wstx.exc.WstxEOFException

Posted by Amila Suriarachchi <am...@gmail.com>.
On Thu, Feb 11, 2010 at 2:26 AM, Colin Sharples [DATACOM] <
Colin.Sharples@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.Sharples@datacom.co.nz | Mob: +64-27-457-6628
>
>
>



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