I'm not sure I can help further unless you want to send me a copy of your .jmx file 
and a copy of a the test log with functional testing turned on (run just once through 
test plan).

-Mike

On 4 Sep 2002 at 11:30, Zazueta, Robert wrote:

> Yup, on both of them.
> 
> -----Original Message-----
> From: Mike Stover [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 04, 2002 11:28 AM
> To: JMeter Users List
> Subject: RE: Link Parser
> 
> 
> Did you make sure to choose GET as the method for that second HTTP Request?
> 
> -Mike
> 
> On 4 Sep 2002 at 11:27, Zazueta, Robert wrote:
> 
> > This may be part of the problem: most of the links off of that inital page
> > are relative (i.e. /whatever/index.html rather than
> > http://www.whatever.com/whatever/index.html). So I took off the port in
> the
> > second HTTP Request. Didn't fix it. I added .* as the domain. Not it comes
> > up with http://.*:80/.*.
> > 
> > Any ideas?
> > 
> > Rob Z.
> > 
> > -----Original Message-----
> > From: Mike Stover [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, September 04, 2002 11:08 AM
> > To: JMeter Users List
> > Subject: Re: Link Parser
> > 
> > 
> > I just tried a similar setup and it worked ok.  My guess is that the page
> > returned by your first 
> > request doesn't return links that match, maybe because of the non-default
> > port number.  
> > 
> > -Mike
> > 
> > On 4 Sep 2002 at 10:29, Zazueta, Robert wrote:
> > 
> > > Hey y'all. New to the list. I just went through the archives and found
> > most
> > > of the answer I was lookinf for in regards to using the link parser as
> > part
> > > of a spidering tool (I actually *do* see some use to doing this for our
> > > site). Everything is more or less copasetic except for one thing: it
> > doesn't
> > > seem to like regular expressions in the path of the HTTP Request.
> > > 
> > > Here's what I'm using:
> > >   JDK 1.3.1
> > >   JMeter 1.7.3
> > >   Windows 2000
> > > 
> > > Here's how it's set up:
> > > 
> > > Root
> > >   Test Plan
> > >           Thread Group
> > >                   HTTP Request (Domain: my-machine, Port: 5000 Path:
> > > /)
> > >                   Simple Controller
> > >                           HTTP HTML Link Parser
> > >                           HTTP Request (Domain: my-machine, Port: 5000
> > > Path: .*)
> > >                   Constant Timer (3000ms)
> > >                   View Results Tree
> > >                   HTTP Cookie Manager
> > > WorkBench
> > > 
> > > The results tree show just fine for the first HTML Request. For the
> second
> > > one, though, the request data is "http://my-machine:5000/.*"; and the
> HTTP
> > > Response code is a Non HTTP Response Code. The HTTP response Message is
> --
> > > you guessed it -- a Non HTTP response message.
> > > 
> > > Any idea what I'm doing wrong here? Thanks!
> > > 
> > > Rob Z.
> > > 
> > > 
> > > --
> > > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > 
> > 
> > 
> > 
> > --
> > Michael Stover
> > [EMAIL PROTECTED]
> > Yahoo IM: mstover_ya
> > ICQ: 152975688
> > 
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > 
> > 
> > --
> > To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> > 
> 
> 
> 
> --
> Michael Stover
> [EMAIL PROTECTED]
> Yahoo IM: mstover_ya
> ICQ: 152975688
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 



--
Michael Stover
[EMAIL PROTECTED]
Yahoo IM: mstover_ya
ICQ: 152975688

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to