Thanks for the tips. This is very strange. I can't get this to work at all,
and I don't know why. I just realised that I had answered the earlier thread
regarding this problem (and I was probably stopped by some other issue which
made me forget to send the test case back then). Anyway, this is the very
same problem
http://www.nabble.com/JMeter-2.2-Extractor-Variable-Problems-tf1786056.html#a5064504
Was this discussed anywhere else? Sebb, are you using 2.2 or some later
nightly build?
/Per
From: sebb <[EMAIL PROTECTED]>
Reply-To: "JMeter Users List" <[email protected]>
To: "JMeter Users List" <[email protected]>
Subject: Re: Can't use Reqular Extraction Variable in request path
Date: Fri, 8 Sep 2006 17:39:54 +0100
If the RE extractor runs at all, then the variable will be set to
either the default, or the extracted information.
The presence of the untranslated ${Variable} in the output means that
the variable "Variable" is not defined at all. So either the RE has
failed to run, or the variable name is misspelt.
I've tried running the test you sent me privately, and the REs seem to
work fine, even though I cannot access the server - they all return
"Error" as expected.
I suggest you check jmeter.log, in case there is some error that is
causing the RE to fail to run properly (unlikely, but worth checking).
On 08/09/06, Per Ekman <[EMAIL PROTECTED]> wrote:
Yeah, I'll send you the test case and check the archives
It shouldn't be an incorrect regexp expression, as the default value
should
then be inserted into the request path instead of ${LocationHeader1}
>From: sebb <[EMAIL PROTECTED]>
>Reply-To: "JMeter Users List" <[email protected]>
>To: "JMeter Users List" <[email protected]>
>Subject: Re: Can't use Reqular Extraction Variable in request path
>Date: Thu, 7 Sep 2006 18:52:05 +0100
>
>I seem to remember someone else reported this problem, but I cannot
>remember the resolution. Check the mail archives.
>
>If this does not show the solution, perhaps you can you send me the
>JMX privately - or perhaps create a Bugzilla issue.
>
>[Please don't post it to the mailing list]
>
>On 07/09/06, Per Ekman <[EMAIL PROTECTED]> wrote:
>>Hi
>>
>>I'm trying out jMeter2.2 and using an old test case developed in 2.1.
My
>>test case uses a regular expression extractor in order to fetch the
>>location
>>header in a request and save it in a variable.
>>
>>So I'm using a variable like this: ${LocationHeader1} in the path and
when
>>the request is sent it looks like this in the View Result Tree: GET
>>http://130.100.12.34/${LocationHeader1}
>>
>>However, something is fishy here. In the same test case I have managed
to
>>extract a header in this way and use in a request.
>>
>>Does anyone have a similar problem, and if so a possible solution?
>>
>>_________________________________________________________________
>>Lyssna obegränsat på musik! http://www.msn.se/music
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
_________________________________________________________________
Windows Live Messenger är här! http://get.live.com/messenger/overview
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Sök bilder på kändisar! http://search.msn.se/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
