Bug 41416

Summary:	Regular Expression Extractor does not work anymore
Product:	JMeter - Now in Github	Reporter:	Holger Isenberg <isenberg>
Component:	Main	Assignee:	JMeter issues mailing list <issues>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	P3
Version:	Nightly (Please specify date)
Target Milestone:	---
Hardware:	All
OS:	All
Bug Depends on:	41414
Bug Blocks:
Attachments:	simple regular extraction test

Description Holger Isenberg 2007-01-19 08:40:05 UTC

With SVN revision 497856 on rel-2-2 Regular Expression Extractor does 
not work anymore on Mac OS X. About a month ago all was fine. Tested 
with all current Java versions on Mac (1.4.2, 1.5.0, 1.6.0).

When the small patch for Mac at #41414 is included into the nightly 
builds, I'll try that compiled version.

Comment 1 Sebb 2007-01-21 15:45:39 UTC

Have you been able to try the latest nightly build?

Exactly what does not work on Mac OS X - any errors in jmeter.log?

Comment 2 Holger Isenberg 2007-01-22 02:26:00 UTC

Created attachment 19441 [details]
simple regular extraction test

This JMX-script does not work anymore with the current nightly build
(2007/01/21)

Comment 3 Holger Isenberg 2007-01-22 02:32:43 UTC

(In reply to comment #1)
> Have you been able to try the latest nightly build?
> 
> Exactly what does not work on Mac OS X - any errors in jmeter.log?

First, I thought the reason was my build process on Mac OS. Now I 
checked again with the nightly build (2007/01/21): The error seems to 
be independent from operating system as the attached simple test  
also failed on Windows. The variable ${title} stays on the initial 
value of "0" set by "User Variables". When not listed on "User 
Variables" the value of ${title} is set to "${title}" instead of the 
extraction result or the default value "-1".

Comment 4 Holger Isenberg 2007-01-24 01:55:08 UTC

Failed with nightly build jakarta-jmeter-2-2.20070122_*.zip on all 
operating systems. Tested with Java 1.5 and 1.6 on Windows, Linux, 
Mac.

Comment 5 Sebb 2007-01-24 11:50:48 UTC

If you uncomment the following jmeter.property it will work:

jmeterthread.reversePostProcessors=true

The new default is invoke PostProcessors to work in forward order.

Oops! Although I reversed the list scanning, I overlooked the iterator setup 
call.

This was setting the position to the last entry - so of course it does not find 
any later entries.

Try the next nightly build, and it should work OK again - but in the forward 
order.

Thanks for reporting the bug.

Comment 6 Holger Isenberg 2007-01-24 13:04:24 UTC

Thanks for the quick fix!

With 20070124 it does work now, independent from 
jmeterthread.reversePostProcessors settings.

Comment 7 The ASF infrastructure team 2022-09-24 20:37:38 UTC

This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1850