On Wed, Sep 16, 2009 at 6:35 PM, Moley Harey <moleyha...@gmail.com> wrote:

> Hi, yes here is the error trace in the server side:
> org.apache.axis2.AxisFault
>         at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>         at
> org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83)
>         at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:337)
>         at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:214)
>         at
> org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530)
>         at
> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:416)
>         at
> org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:379)
>         at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:167)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
>         at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
>         at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
>         at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:619)
> Caused by: com.ctc.wstx.exc.WstxIOException: null
>         at
> com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313)
>         at
> org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:146)
>         at
> org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:472)
>         at
> org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79)
>         ... 20 more
> Caused by: ClientAbortException:  java.net.SocketException: Broken pipe
>         at
> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:319)
>         at
> org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
>         at
> org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)
>         at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99)
>         at
> com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214)
>         at
> com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:311)


this happens due to time out in client side. So increase the client side
time you using the above mentioned option.

thanks,
Amila.

>
>
>
> 2009/9/16 Chinmoy Chakraborty <cch...@gmail.com>
>
>> do you have any exception in the server side? send me the complete stack
>> trace...you can also put a breakpoint and debug...
>>
>>
>>
>>
>>
>> On Wed, Sep 16, 2009 at 3:24 PM, Moley Harey <moleyha...@gmail.com>wrote:
>>
>>> Hi again,
>>> I am getting the following exception: "org.apache.axis2.AxisFault: Read
>>> timed out"
>>>
>>> I have generated the Client-side stub classes to connect with my web
>>> service using the wsdl2java Tool, in which class of the Client-side stub
>>> should i set this "options.setTimeOutInMilliSeconds(600000);" code? In the
>>> Skeleton one?
>>>
>>> Also, is possible to configure the timeout in the server side using the
>>> axsi2.xml paremeter "ConfigContextTimeoutInterval"?
>>>
>>> The default value for Axis2 web services timeout is 60 seconds, isn't it?
>>>
>>> thank you,
>>>
>>> Mh
>>>
>>> 2009/9/16 Chinmoy Chakraborty <cch...@gmail.com>
>>>
>>>  what exception you are getting? can you share your log?
>>>>
>>>> yes you can configure timeout in the client side..like
>>>> options.setTimeOutInMilliSeconds(600000);
>>>>
>>>>   On Wed, Sep 16, 2009 at 2:12 PM, Moley Harey <moleyha...@gmail.com>wrote:
>>>>
>>>>> Hi folks!
>>>>>
>>>>> I have implemented an Axis2 web service to retrieve some publication
>>>>> data stored remotely in a web server.
>>>>> I have done some tests and everything runs well but I have noticed that
>>>>> if I do several consecutive calls to the web service I receive "Timeouts"
>>>>> responses in the client side and I see that Axis exception in my log 
>>>>> files.
>>>>>
>>>>> Is there any way to configure the timeout response in my web service?
>>>>> Or that timeout should be configured in the Client-side?
>>>>>
>>>>> thank you,
>>>>>
>>>>> Mh
>>>>>
>>>>
>>>>
>>>
>>
>


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

Reply via email to