You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by "Emerson, David" <DE...@emptoris.com> on 2002/08/29 16:26:53 UTC

HTTP Proxy Server problems

I'm trying to use the proxy server to record test plan script and I'm having
trouble. I"ve had previous success recording (a few nightly builds from
about a month ago) but it no longer works for me. I've added the HTTP Proxy
Server to the Workbench, added a Thread Group and Cookie Manager to the
Thread Group and started the server. I'm using IE 5.5 and set up the
connection to go through the proxy. The application is being tested on a
small isolated network with JSP requests being forwarded to Weblogic on an
app server on the network. The application's UI uses multiple frames. A few
gifs, js, and the login jsp are recorded but at that point the app seems to
hang. The IE busy indicator was still 'spinning'. It seems like the web
server (IIS) is waiting on some sort of reponse from the browser that never
appears. I'd really like to be able to use JMeter but I'm hoping you have
suggestions on how to debug this problem.
Thanks.


Re: HTTP Proxy Server problems

Posted by Eric Siegerman <er...@telepres.com>.
On Thu, Aug 29, 2002 at 10:26:53AM -0400, Emerson, David wrote:
> I'm trying to use the proxy server [...]
> It seems like the web
> server (IIS) is waiting on some sort of reponse from the browser that never
> appears. I'd really like to be able to use JMeter but I'm hoping you have
> suggestions on how to debug this problem.

Check out Ethereal -- www.ethereal.com.  A great GPL'ed packet
sniffer.  I used it a couple of weeks ago to track down some
problems I was having with the JMeter proxy.

Features likely to be of use are "Decode As..." and "Follow TCP
Stream", both on the right-click menu once you've selected a TCP
packet of interest.  With the former, you can tell it which
upper-layer protocol the TCP connection is carrying (e.g. HTTP);
with the latter, you can get a dump (ASCII or hex) of the entire
HTTP (or whatever) conversation, without having to trace through
all the packets yourself.

I found it useful to sniff a fetch without the proxy involved;
then both sides of a fetch with the proxy (i.e. both the browser
side and the server side), then compare the three streams.

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        erics@telepres.com
|  |  /
Anyone who swims with the current will reach the big music steamship;
whoever swims against the current will perhaps reach the source.
	- Paul Schneider-Esleben

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>