Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of woolfel@gmail.com designates
 64.233.170.193 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=qkXWhcMukARk4yIWa7FDtCuj+uLo4a0ORqygKG3ocMqm4day2usC2vVAtZgkKhLx7TzRXbjh8d7wWlHEGcdJb4G9RDCWf7EHiV+fiC6vS9WU1KqY5d199gzt8vFHZhBy0Bkb9jkQhpMxX5XpzpIEZTrtSMkgKHK9+jw3vaKH00A=
Message-ID: <27e674a9050615090831e7e9b3@mail.gmail.com>
Date: Wed, 15 Jun 2005 12:08:34 -0400
From: Peter Lin <woolfel@gmail.com>
Reply-To: Peter Lin <woolfel@gmail.com>
To: JMeter Users List <jmeter-user@jakarta.apache.org>,
	Bronagh.McElduff@mobilecohesion.com
Subject: Re: Multiple port configuration
In-Reply-To: <42B0443F.6070604@mobilecohesion.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <42AFDFEB.8040800@mobilecohesion.com>
	 <1118842101.5036.24.camel@P78WVP51-udp504000uds.ams.gblxint.com>
	 <42B0443F.6070604@mobilecohesion.com>

looking at your email address, I'm guessing you're working on mobile
applications.

for async webservices, I'm bias against HTTP. Several months back I
considered writing a J2ME JMS driver for SideKickII, so that I could
use JMS to send/recieve Multimedia messages.

Using HTTP for Async messages is an ugly hack and ultimately isn't
going to scale very well. I know ObjectWeb has KJoram for J2ME and IBM
has a J2ME client for MQSeries. In theory, writing an async HTTP
client isn't all that hard, but the catch is you really do need to use
Keep alive connections.

Depending on the type of wireless device, and whether it has a
dynamic/static IP, sending the response back to the client may not be
feasible without keeping the connection alive. I would strongly
recommend looking at JMS approach rather than async HTTP. Even though
the data rates for mobile phones have improved, a page that is large
will have a hard time getting through reliably. this is still true
today in ATT, and Verizon data services.

I hope that helps

peter


On 6/15/05, Bronagh McElduff <Bronagh.McElduff@mobilecohesion.com> wrote:
> Hi Michael,
>=20
> Basically our application uses SOAP-based communication, mainly XML. It
> receives a SOAP messages, and sends back a meaningless response. It is
> only later when our application informs the client, using an HTTP
> request on the client, about the results of the processing. It is these
> so-called /asynchronous SOAP messages/ (transported over HTTP) that I am
> interested in capturing.
>=20
> Can JMeter be configured or extended to mimic this behaviour?
>=20
> Thanks in advance,
> Bronagh
>=20
> Michael Stover wrote:
>=20
> >How do clients use your app?  Is every client a server?  If so, JMeter
> >is not designed to mimic such behavior.
> >
> >-Mike
> >
> >On Wed, 2005-06-15 at 08:59 +0100, Bronagh McElduff wrote:
> >
> >
> >>Hi,
> >>
> >>
> >>
> >>I wish to configure JMeter to submit a message on localhost:9999 and co=
llect this message as it leaves localhost:9191 for example.
> >>
> >>Is this achievable? I have tried various ways to do this but it seems t=
hat it is only possible to test the request / response on the same port.  H=
owever, I specifically need to confirm the modifications that our system ma=
kes to the message as it travels through our system and no simply that the =
message has been successfully received.
> >>
> >>Basically, I need to configure JMeter to act as a client and a server.
> >>
> >>Thanks in advance,
> >>B
> >>
> >>
> >>---------------------------------------------------------------------
> >>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
> >
> >
> >
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>=20
>

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