Sorry,

that doesn't help in my case.

I'm using generated code from the axis2-wsdl2code-maven-plugin.
On the server-side there will be generated allways a MessageReceiver
which extends
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.
Independend on the syncMode for which I tried async and both.
I think there is a missing MessageReceiver which extends 
org.apache.axis2.async.AsyncMessageReceiver, isn't it?

Maybe there is a bug in the Generator plugin.

Has anyone an idea?

Thanks for help

Michael

Am Di 08.01.2008 18:08 schrieb Michele Mazzucco
<[EMAIL PROTECTED]>:

> Michael,
> 
> the empty response is sent back straightaway, before the request is  
> executed.
> In order to sort your problem out you should increase the socket  
> timeout on the client side -- this issue has been discussed several  
> times, search through previous messages.
> 
> 
> HTH,
> Michele
> 
> On 8 Jan 2008, at 15:04, Michael Kopf wrote:
> 
> > Hello,
> >
> > I'm really frustrated.
> > I'm using axis2-1.3.
> > I try to use non-blocking dual connections to call a web service
> > whose
> > work
> > could take a long time, maybe several days.
> > In a testing environment the calling by using dual connections works
> > fine, if
> > the work takes only some seconds.
> > If the work takes more then a half minute I get a
> > SocketTimeOutException. See:
> >
> > 2008-01-08 13:56:09,714 INFO [Axis2 Task]
> > org.apache.axis2.transport.http.HTTPSender:194 Unable to  
> > sendViaPost to
> > url[http://localhost:8060/axis2/services/DPFService]
> > java.net.SocketTimeoutException: Read timed out
> >     at java.net.SocketInputStream.socketRead0(Native Method)
> >     at java.net.SocketInputStream.read(SocketInputStream.java:129)
> >
> >
> > I monitored the traffic with a SoapMonitor and what I recognized is,
> > that the
> > empty response of the first connection with header 'HTTP/1.1 202
> > Accepted'
> > arrives not until the web-service has its work done.
> > But in this case I don't need a dual-connecting communication, do I?
> >
> > Thanks to anyone who could help.
> >
> > Kind regards
> >
> > Michael
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to