You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Sonam Chauhan <so...@ce.com.au> on 2007/10/26 11:17:50 UTC

RE: Distributed testing using Jmeter

Bipin: Adding to what Sebb said... 

webMethods EAI testing (i.e. testing publish-subscribe middleware) is
not too difficult except for one limitation (see below) that you can
usually work around.

What I recommend is have JMeter simulate publishing documents, then
verify that each document arrived at all it's destination (subscriber)
systems. Each EAI system publishing a document type would be represented
by a JMeter test script. The JMeter test threads would each publish a
document, wait a specified time, then test each 'destination' system to
make sure the document were successfully received by the subscribers. 

The "correct" way to do 'subscriber verification' is in parallel -- i.e.
the 'publisher' thread group publish the document, then another
'subscriber' thread group underneath the 'publisher' thread group checks
document receipt in parallel at all the 'destination' systems. 

However, multi-level Thread Groups are not currently possible in JMeter:

	http://issues.apache.org/bugzilla/show_bug.cgi?id=41293 
... but you can usually work around it by checking subscriber systems
serially using carefully timed delays. 

Kind regards,
Sonam Chauhan
-- 
Corporate Express Australia Ltd. 
Phone: +61-2-93350725, Email: sonam.chauhan@ce.com.au

-----Original Message-----
From: sebb [mailto:sebbaz@gmail.com] 
Sent: Wednesday, 29 August 2007 2:42 AM
To: JMeter Users List
Subject: Re: Distributed testing using Jmeter

On 18/08/07, Bipin Thakur <bt...@tibco.com> wrote:
> Hi,
>
> Recently I came to know about Jmeter. It is really a simple and very
useful testing tool.
>
> In addition to the documented feature of distributed testing, I have a
different scenario to test. Let us think of performance testing for a
JMS server where publisher/subscriber are running on a server other than
the JMS Server. I want to run JMS sender application on HOST A, JMS
subscriber application on HOST B and the JMS Server on a third machine
HOST C to simulate a real life scenario. This would need provision of
additional parameters, other than "ProvideURL".

What additional parameters are needed?

> I want to know whether it is possible to make a test plan to do this
kind of distributed testing.

JMeter already supports this sort of distributed testing, at least for
HTTP, FTP, TCP, etc - it can send requests to as many different
servers as you want.

If there is something missing from the JMS Samplers that prevents
this, please say what is missing.

> I would highly appreciate your help and directions in this regard.
>
> Sincere regards,
> Bipin Thakur
>
>

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


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