Well, it is working OK, usually ;) Seriously, I had an issue with script recording under 1.3 - sometimes it works just fine, sometimes the io pipe between jmeter and browser is broken, and that browser is just displaying white screen until it times out. I troubleshooted that problem about half a year ago, realized that it was a problem somewhere deep in java libraries, and than suddenly recollected that jmeter is supposed to be used with 1.4, not 1.3. That issue was even reproducible on different platforms (Linux - Solaris).
No such problems with 1.4. regards, Olek On Mon, 15 Mar 2004, BAZLEY, Sebastian wrote: > Glad it's solved, but JMeter is supposed to be able to work OK on 1.3 ... > > Which version of Java were you using? > > And did my test case fail when you tried it on 1.3 ? > > S. > -----Original Message----- > From: Lay, Peter [mailto:[EMAIL PROTECTED] > Sent: 15 March 2004 15:41 > To: 'JMeter Users List' > Subject: RE: Variables ( ${..} ) not resolving in HTTP Request - path > fiel d(Solved) > > > Sebb, > > Thanks. Your jmeter.log helped, I checked and the java version was 1.3x > not 1.4.2. Fixed that and it works! > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, March 12, 2004 4:16 PM > To: JMeter Users List > Subject: Re: Variables ( ${..} ) not resolving in HTTP Request - path > fiel d > > > I still cannot reproduce the error, but I've created a bugzilla issue: > http://issues.apache.org/bugzilla/show_bug.cgi?id=27634 > and attached the following files: > > testcase (.jmx) > jmeter.properties > jmeter.log > > Please try the testcase using my properties file and compare results. > > > The Bugzilla upload link is called "Create a new attachment (proposed patch, > testcase, etc.)" and is about 10-12 lines from the top > of the page. > > [To download a text attachment, you may need to right-click and select Save > As - or whatever your browser calls it] > > S. > ----- Original Message ----- > From: "Lay, Peter" <[EMAIL PROTECTED]> > To: "'JMeter Users List'" <[EMAIL PROTECTED]> > Sent: Friday, March 12, 2004 7:06 PM > Subject: RE: Variables ( ${..} ) not resolving in HTTP Request - path fiel d > > > > Sorry, you are correct the Path does not contain the host, it has > /subdir/${TestID}. > > How do I upload a test case in Bugzilla? There is no upload option anywhere > that I can find - I wanted to upload a simple .jmx file I did. It has 2 > HTTP Requst and 1 Regular Expression Extractor. > > I will attempt to describe them: > > ->HTTP Request (GET) > [ host: jakarta.apache.org > port: 80 > protocol: http > path: / ] > -> Regular Expression Extractor > [Ref Name: TestID > Reg. Exp: timeout=(.*?)\, > Template: $1$ > Math No.: 0 > Default Value: nothin] > ->HTTP Request (GET) > [host: jakarta.apache.org > port: 80 > protocol: http > path: /images/${TestID} > Param: > Name= Test_ID > Value= $TestID > ] > -> View Results Tree > > ---------------------------------------------- > > Run it and check View Results Tree. The 2nd HTTP Request Data shows > something like this: > > http://jakarta.apache.org/images/${TestID}?Test_ID=5 > > The result should be: > http://jakarta.apache.org/images/5?Test_ID=5 > > Note that ${TestID} is evaluated to 5 for the parameter but not in the PATH > field. > > > -----Original Message----- > From: BAZLEY, Sebastian [mailto:[EMAIL PROTECTED] > Sent: Friday, March 12, 2004 12:23 PM > To: 'JMeter Users List' > Subject: RE: Variables ( ${..} ) not resolving in HTTP Request - path > fiel d > > > The path field should not contain the protocol, host or port. > Just /subdir/${TESTID}. > But whether that is the problem is doubtful. > > If a variable VAR shows up as ${VAR) - i.e. it has not been replaced by its > value - that indicates that the variable could not be found at the time the > parameter containing it was evaluated. > > I created a test plan based on your e-mail, but I've been unable to recreate > the problem. > > If fixing the path as above does not solve the problem, please create a > Bugzilla issue and upload a simple test case to it. > > S. > -----Original Message----- > From: Lay, Peter [mailto:[EMAIL PROTECTED] > Sent: 12 March 2004 14:43 > To: 'JMeter Users List' > Subject: RE: Variables ( ${..} ) not resolving in HTTP Request - path > fiel d > > > Thank you for the reply. Here's my test plan: > > Test Plan > Thread Group > Recording Controller > View Results Tree > HTTP Authorization Manager > HTTP Request > Browser-derived headers > Regular Expression Extractor <-- grabs id, > assign TESTID variable > HTTP Request <- Path field has > http://server/subdir/${TESTID} > > I view the Results Tree and looked at 2nd HTTP Request data - it shows > "http://server/subdir/${TESTID}";. TESTID should resolve and contain a value > extracted by Regular Expression Extractor but it doesn't. Grrrrrr... If I > put ${TESTID} in the Parameter section in the 2nd HTTP Request, it resolves > to the value extracted by "Regular Expression Extractor". > > My OS is NT 4.0 SP6 and JMeter.bat dated 8/17/2003 v.1.9.1 > > Lastly, if I added a "HTTP URL Re-writing Modifier" with "Path Extension" > checked, ${TESTID} does resolve in the Path field but it adds the ";" at > end, which is an invalid URL. Sigh... Please help. > > Thanks again, > /peter > > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 11, 2004 6:58 PM > To: JMeter Users List > Subject: Re: Variables ( ${..} ) not resolving in HTTP Request - path > field > > > Works for me in the current CVS release. > > Also works for me in 1.9.1. > > Please can you post a simple test case to Bugzilla? > > ----- Original Message ----- > From: "Lay, Peter" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, March 11, 2004 10:04 PM > Subject: Variables ( ${..} ) not resolving in HTTP Request - path field > > > Hi All, > > I successfully extracted a value from a previous response and assigned it to > a variable. The variable is resolved in the Parameter section of HTTP > Request but not in the Path field. It seems it gets resolved everywhere but > the Path field - I tried it on the Server Name and it works but not in the > Path field. Any help is appreciated. > > Thanks, > /peter > > > > > > ************************************************************************** > This e-mail and any files transmitted with it may contain privileged or > confidential information. It is solely for use by the individual for whom > it is intended, even if addressed incorrectly. If you received this e-mail > in error, please notify the sender; do not disclose, copy, distribute, or > take any action in reliance on the contents of this information; and delete > it from your system. Any other use of this e-mail is prohibited. Thank you > for your compliance. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > ___________________________________________________________________________ > > This e-mail and the documents attached are confidential and intended solely > for the addressee; it may also be privileged. If you receive this e-mail in > error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Atos Origin group liability cannot be > triggered for the message content. Although the sender endeavours to > maintain > a computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted. > ___________________________________________________________________________ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > ************************************************************************** > This e-mail and any files transmitted with it may contain privileged or > confidential information. It is solely for use by the individual for whom > it is intended, even if addressed incorrectly. If you received this e-mail > in error, please notify the sender; do not disclose, copy, distribute, or > take any action in reliance on the contents of this information; and delete > it from your system. Any other use of this e-mail is prohibited. Thank you > for your compliance. > > > > > --------------------------------------------------------------------- > 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] > > > > ************************************************************************** > This e-mail and any files transmitted with it may contain privileged or > confidential information. It is solely for use by the individual for whom > it is intended, even if addressed incorrectly. If you received this e-mail > in error, please notify the sender; do not disclose, copy, distribute, or > take any action in reliance on the contents of this information; and delete > it from your system. Any other use of this e-mail is prohibited. Thank you > for your compliance. > > > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
