Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <user@jmeter.apache.org>
Received-SPF: pass (athena.apache.org: domain of asp.adieu@gmail.com
 designates 209.85.214.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1599059341.22200.1359469195881.JavaMail.root@mbox03.in.post.sk>
References: <948042347.22130.1359469116240.JavaMail.root@mbox03.in.post.sk>
	<1599059341.22200.1359469195881.JavaMail.root@mbox03.in.post.sk>
Date: Tue, 5 Feb 2013 16:15:14 +0200
Message-ID: 
 <CANEEAcxPey90zgDwUSkAVKz0YcPddwmTUFO4GJqnTk4sWkxMdg@mail.gmail.com>
Subject: Re: Testing asynchronous webservices
From: Adrian Speteanu <asp.adieu@gmail.com>
To: JMeter Users List <user@jmeter.apache.org>
Content-Type: multipart/alternative; boundary=14dae93a1145a38abd04d4fad6d3

--14dae93a1145a38abd04d4fad6d3
Content-Type: text/plain; charset=UTF-8

Hi,

This applies in general (unfortunately):
If you want to have some smart way of doing the same stuff your client app
does, then you'll have to extend JMeter, which is rather easy, especially
if you already have the jars that implement the logic you need. Otherwise,
once you've configured the web-service sampler properly, the issues of
testing web-services are the same as in the case of any other apps.

Except: "AWS callback with info -> APP", I wouldn't know how to test this
in JMeter without extending it. Its not a behaviour I've encountered
before. The timeout works for responses to outgoing calls, but we're not
there yet with this requirement.

And because you made me curious, I googled a bit, found this:
http://www.codeaffine.com/2011/11/28/stressload-testing-of-asynchronous-httprest-services-with-jmeter/Apparently
they didn't had that problem, their challenge was similar to
what I expected, client initiated transactions and large response times in
some cases (the blog has some interesting ideas for you). Make sure you
really have to wait for a callback initiated by the server first (very few
systems use it). But if it does do that, would be nice of you to let us
know what solution you guys eventually picked.

Adrian S

On Tue, Jan 29, 2013 at 4:19 PM, Stefan Pivoda <spaghi@post.sk> wrote:

> Hi All,
>
> Has anybody experience with testing asynchronous web-services with Jmeter?
>
> Could you please describe me how to configure and test:
>
>     whether i receive a confirmation from the async web-service;
>     after that how to set some daemon that will wait for the callback with
> the requested information from that async web-service;
>     evaluate whether this received response from the callback.
>
> The communication between the APP and the async web-service (AWS) should
> look like this:
>
>     APP request -> (AWS)
>     AWS confirmation -> APP
>     AWS callback with info -> APP
>     APP confirmation -> AWS
>
> I dont want to set some specific long time-out and just wait for the
> callback, if it is not needed as it will be different in each case base on
> the method in the background that the async webservice will handle. that's
> the reason why i'd like to use some deamon or some more sophisticated way,
> if it is possible.
>
> thank you
> Stefan
> _____________________________________________________________________
>
> Vsetko podstatne z vedy, pocitacov,  mobilov aj hier -
> http://www.TECHsme.sk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>

--14dae93a1145a38abd04d4fad6d3--