Hi Sagara, The following concern was identified during a customer query. Any feedback is much appreciated.
Best regards, Amal. On Thu, Apr 23, 2015 at 10:27 AM, Amal Gunatilake <[email protected]> wrote: > Hi Guys, > > Appreciate any thoughts on the above matter. :) > > Best regards, > Amal. > > On Tue, Apr 21, 2015 at 4:01 PM, Amal Gunatilake <[email protected]> wrote: > >> Hi Sameera and Team, >> >> I wrote a simple Axis2 sample with a 10 seconds delay in between the >> message receive and response. Then I invoke the service using SoapUI and >> before (in-between 10s delay) sending the response, I terminate the >> connection. When the server reply back with the response, it's unable to >> write the message and therefore theoretically it should throw an exception, >> but there's no error logged in the server end. >> >> The requirement is, since Axis2 is HTTP transport there has to be an ACK >> for each and every receive and response and if something goes wrong with >> the connection when writing the response there has to be an exception >> thrown. This is mainly to identify the difference between a response that >> has been written successfully and a response that was unable to write due >> to broken pipe. >> >> Please advice me whether this is already implemented in the carbon code >> base and if not how can we achieve this requirement in Axsi2? >> >> Kind regards, >> >> *Amal Gunatilake* >> Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> > > > > -- > Kind regards, > > *Amal Gunatilake* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > -- Kind regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
