Ok, i'll try that different regex tonight. Also; no errors or warnings in the jmeter log i'm afraid!
Rgds, Dan > On 24/05/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> > >> > Perhaps there is a thread-safety problem. >> > Does the RE use fixed strings, or are any variables used? >> > >> >> The regex is simply: >> >> <value>(.+?)< >> looking for the 16th match. The default value is "unset" > >>From the performance aspect it might be worth trying > > <value>([^<]+) > > as this does not require lookahead. > >> > How many threads in the thread group? >> >> This particular thread group has 10 threads. over all there are about >> 550 >> in use. The group itself has a read from csv, a counter, 2 samplers, >> the >> 2 regex's and finally a constant throughput timer. > > OK. > >> >> >> the point, how can I investigate further? >> > >> > You could use the "Save Responses" Post-Processor as a child of the >> > samplers to create a copy of all the responses. >> >> I can already see the responses in our database. AFAIKT there's no way >> they could be any different to what comes out at the jmeter end, but >> i'll >> have a try. > > Should not be different, but they are presumably at different ends of > a network connection, so it's remotely (!) possible. > >> > Is there any pattern to the failures? >> > Do they match the wrong text, or do they fail to match at all? >> >> It seems to fail completely - I get the "unset" (default value) which >> doesnt appear in the xml response at all, rather than the wrong value. > > Any error/warning messages in the jmeter log file? > > S. > > --------------------------------------------------------------------- > 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]
