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 Sathwik <ba...@intalio.com> on 2011/09/13 13:11:51 UTC

[Axis2] EchoNonBlockingDualClient sample ACK and Response arrive at the same time

Hi,

When I run the sample EchoNonBlockingDualClient, I see that the HTTP 202 
ACK and the Response are arriving at the same time. I have a 30 second 
sleep in the MyService.echo() method to simulate late response.

I am herewith attaching the req-ack captured on TCP-Mon. Resp printed on 
the client console.

ACK time: Since in GMT, will need to add 5 hrs 30 min 30 sec which is 
17:45:42
Now if we compare it with  response time [java] >>>>>> Time end: Fri Sep 
09 17:45:12 IST 2011, they are absolutely equal.

So my question is that shouldn't  the ACK come earlier than the 
response. Can anyone please let me know if it is the intended behavior.

===========Request===================
POST /axis2/services/MyService HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: "urn:echo"
User-Agent: Axis2
Host: 127.0.0.1:8888
Transfer-Encoding: chunked

288
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://127.0.0.1:8888/axis2/services/MyService</wsa:To><wsa:ReplyTo><wsa:Address>http://10.10.2.134:6060/axis2/services/anonService2/</wsa:Address></wsa:ReplyTo><wsa:MessageID>urn:uuid:f99ffeec-fb5b-4b98-bb3b-9d83f0635be9</wsa:MessageID><wsa:Action>urn:echo</wsa:Action></soapenv:Header><soapenv:Body><example1:echo 
xmlns:example1="http://example1.org/example1"><example1:Text>Axis2 Echo 
String </example1:Text></example1:echo></soapenv:Body></soapenv:Envelope>
0


=============ACK=====================
HTTP/1.1 202 Accepted
Date: Fri, 09 Sep 2011 12:15:12 GMT
Server: Simple-Server/1.1
Transfer-Encoding: chunked

0


==========Response printed on client console==========
      [java] Time start: Fri Sep 09 17:44:41 IST 2011
      [java] sendReceiveNonBlocking:Fri Sep 09 17:44:41 IST 2011
      [java] <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://10.10.2.134:6060/axis2/services/anonService2/</wsa:To><wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address></wsa:ReplyTo><wsa:MessageID>urn:uuid:2d3b7bde-f31d-42f5-8c0a-1bf92387ebfc</wsa:MessageID><wsa:Action>urn:echoResponse</wsa:Action><wsa:RelatesTo>urn:uuid:f99ffeec-fb5b-4b98-bb3b-9d83f0635be9</wsa:RelatesTo></soapenv:Header><soapenv:Body><example1:echo 
xmlns:example1="http://example1.org/example1"><example1:Text>Axis2 Echo 
String </example1:Text></example1:echo></soapenv:Body></soapenv:Envelope>
      [java] >>>>>> Time end: Fri Sep 09 17:45:12 IST 2011
      [java] [SimpleHTTPServer] Stop called

regards,
sathwik

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org


Re: [Axis2] EchoNonBlockingDualClient sample ACK and Response arrive at the same time

Posted by Sathwik <ba...@intalio.com>.
Hi amila,
Thanks for your reply. It works after setting the parameter in service.xml
regards,
sathwik

On Wednesday 14 September 2011 12:31 PM, Amila Suriarachchi wrote:
> if you have set the messageReceiver.invokeOnSeparateThread in your 
> service.xml
>
> then it sends the 202 accept before sending response.
>
> thanks,
> Amila.
>
> On Tue, Sep 13, 2011 at 4:41 PM, Sathwik 
> <bantwalpremakumar@intalio.com <ma...@intalio.com>> 
> wrote:
>
>     Hi,
>
>     When I run the sample EchoNonBlockingDualClient, I see that the
>     HTTP 202 ACK and the Response are arriving at the same time. I
>     have a 30 second sleep in the MyService.echo() method to simulate
>     late response.
>
>     I am herewith attaching the req-ack captured on TCP-Mon. Resp
>     printed on the client console.
>
>     ACK time: Since in GMT, will need to add 5 hrs 30 min 30 sec which
>     is 17:45:42
>     Now if we compare it with  response time [java] >>>>>> Time end:
>     Fri Sep 09 17:45:12 IST 2011, they are absolutely equal.
>
>     So my question is that shouldn't  the ACK come earlier than the
>     response. Can anyone please let me know if it is the intended
>     behavior.
>
>     ===========Request===================
>     POST /axis2/services/MyService HTTP/1.1
>     Content-Type: text/xml; charset=UTF-8
>     SOAPAction: "urn:echo"
>     User-Agent: Axis2
>     Host: 127.0.0.1:8888 <http://127.0.0.1:8888>
>     Transfer-Encoding: chunked
>
>     288
>     <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
>     xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header
>     xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://127.0.0.1:8888/axis2/services/MyService</wsa:To><wsa:ReplyTo><wsa:Address>http://10.10.2.134:6060/axis2/services/anonService2/</wsa:Address></wsa:ReplyTo><wsa:MessageID>urn:uuid:f99ffeec-fb5b-4b98-bb3b-9d83f0635be9</wsa:MessageID><wsa:Action>urn:echo</wsa:Action></soapenv:Header><soapenv:Body><example1:echo
>     xmlns:example1="http://example1.org/example1"><example1:Text>Axis2
>     Echo String
>     </example1:Text></example1:echo></soapenv:Body></soapenv:Envelope>
>     0
>
>
>     =============ACK=====================
>     HTTP/1.1 202 Accepted
>     Date: Fri, 09 Sep 2011 12:15:12 GMT
>     Server: Simple-Server/1.1
>     Transfer-Encoding: chunked
>
>     0
>
>
>     ==========Response printed on client console==========
>         [java] Time start: Fri Sep 09 17:44:41 IST 2011
>         [java] sendReceiveNonBlocking:Fri Sep 09 17:44:41 IST 2011
>         [java] <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope
>     xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header
>     xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:To>http://10.10.2.134:6060/axis2/services/anonService2/</wsa:To><wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address></wsa:ReplyTo><wsa:MessageID>urn:uuid:2d3b7bde-f31d-42f5-8c0a-1bf92387ebfc</wsa:MessageID><wsa:Action>urn:echoResponse</wsa:Action><wsa:RelatesTo>urn:uuid:f99ffeec-fb5b-4b98-bb3b-9d83f0635be9</wsa:RelatesTo></soapenv:Header><soapenv:Body><example1:echo
>     xmlns:example1="http://example1.org/example1"><example1:Text>Axis2
>     Echo String
>     </example1:Text></example1:echo></soapenv:Body></soapenv:Envelope>
>         [java] >>>>>> Time end: Fri Sep 09 17:45:12 IST 2011
>         [java] [SimpleHTTPServer] Stop called
>
>     regards,
>     sathwik
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>     <ma...@axis.apache.org>
>     For additional commands, e-mail: java-user-help@axis.apache.org
>     <ma...@axis.apache.org>
>
>
>
>
> -- 
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org


Re: [Axis2] EchoNonBlockingDualClient sample ACK and Response arrive at the same time

Posted by Amila Suriarachchi <am...@gmail.com>.
if you have set the messageReceiver.invokeOnSeparateThread in your
service.xml

then it sends the 202 accept before sending response.

thanks,
Amila.

On Tue, Sep 13, 2011 at 4:41 PM, Sathwik <ba...@intalio.com>wrote:

> Hi,
>
> When I run the sample EchoNonBlockingDualClient, I see that the HTTP 202
> ACK and the Response are arriving at the same time. I have a 30 second sleep
> in the MyService.echo() method to simulate late response.
>
> I am herewith attaching the req-ack captured on TCP-Mon. Resp printed on
> the client console.
>
> ACK time: Since in GMT, will need to add 5 hrs 30 min 30 sec which is
> 17:45:42
> Now if we compare it with  response time [java] >>>>>> Time end: Fri Sep 09
> 17:45:12 IST 2011, they are absolutely equal.
>
> So my question is that shouldn't  the ACK come earlier than the response.
> Can anyone please let me know if it is the intended behavior.
>
> ===========Request============**=======
> POST /axis2/services/MyService HTTP/1.1
> Content-Type: text/xml; charset=UTF-8
> SOAPAction: "urn:echo"
> User-Agent: Axis2
> Host: 127.0.0.1:8888
> Transfer-Encoding: chunked
>
> 288
> <?xml version='1.0' encoding='UTF-8'?><soapenv:**Envelope xmlns:soapenv="
> http://schemas.**xmlsoap.org/soap/envelope/<http://schemas.xmlsoap.org/soap/envelope/>
> "><**soapenv:Header xmlns:wsa="http://www.w3.org/**2005/08/addressing<http://www.w3.org/2005/08/addressing>
> "><wsa:To>ht**tp://127.0.0.1:8888/axis2/**services/MyService<http://127.0.0.1:8888/axis2/services/MyService>
> </wsa:To><**wsa:ReplyTo><wsa:Address>http:**//10.10.2.134:6060/axis2/**
> services/anonService2/<http://10.10.2.134:6060/axis2/services/anonService2/>
> </wsa:**Address></wsa:ReplyTo><wsa:**MessageID>urn:uuid:f99ffeec-**
> fb5b-4b98-bb3b-9d83f0635be9</**wsa:MessageID><wsa:Action>urn:**
> echo</wsa:Action></soapenv:**Header><soapenv:Body><**example1:echo
> xmlns:example1="http://**example1.org/example1<http://example1.org/example1>
> "><**example1:Text>Axis2 Echo String </example1:Text></example1:**
> echo></soapenv:Body></soapenv:**Envelope>
> 0
>
>
> =============ACK==============**=======
> HTTP/1.1 202 Accepted
> Date: Fri, 09 Sep 2011 12:15:12 GMT
> Server: Simple-Server/1.1
> Transfer-Encoding: chunked
>
> 0
>
>
> ==========Response printed on client console==========
>     [java] Time start: Fri Sep 09 17:44:41 IST 2011
>     [java] sendReceiveNonBlocking:Fri Sep 09 17:44:41 IST 2011
>     [java] <?xml version='1.0' encoding='utf-8'?><soapenv:**Envelope
> xmlns:soapenv="http://schemas.**xmlsoap.org/soap/envelope/<http://schemas.xmlsoap.org/soap/envelope/>
> "><**soapenv:Header xmlns:wsa="http://www.w3.org/**2005/08/addressing<http://www.w3.org/2005/08/addressing>
> "><wsa:To>ht**tp://10.10.2.134:6060/axis2/**services/anonService2/<http://10.10.2.134:6060/axis2/services/anonService2/>
> </wsa:**To><wsa:ReplyTo><wsa:Address>h**ttp://www.w3.org/2005/08/**
> addressing/none <http://www.w3.org/2005/08/addressing/none></wsa:Address><
> **/wsa:ReplyTo><wsa:MessageID>**urn:uuid:2d3b7bde-f31d-42f5-**
> 8c0a-1bf92387ebfc</wsa:**MessageID><wsa:Action>urn:**
> echoResponse</wsa:Action><wsa:**RelatesTo>urn:uuid:f99ffeec-**
> fb5b-4b98-bb3b-9d83f0635be9</**wsa:RelatesTo></soapenv:**
> Header><soapenv:Body><**example1:echo xmlns:example1="http://**
> example1.org/example1 <http://example1.org/example1>"><**example1:Text>Axis2
> Echo String </example1:Text></example1:**echo></soapenv:Body></soapenv:**
> Envelope>
>     [java] >>>>>> Time end: Fri Sep 09 17:45:12 IST 2011
>     [java] [SimpleHTTPServer] Stop called
>
> regards,
> sathwik
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.**apache.org<ja...@axis.apache.org>
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>


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