RE: JMeter from time to time doesn't calculate regular expression s for some threads

["BAZLEY, Sebastian" <Se...@london.sema.slb.com>]

>-----Original Message-----
>From: Vladimir Tsygankov [mailto:Vladimir@contera.sp.ru]
>Sent: 09 February 2004 18:02
>To: 'JMeter Users List'
>Subject: RE: JMeter from time to time doesn't calculate regular
>expressions for some threads
>
>
>Hello, colleagues,
>I'm returning to the problem of "Regular expression problem for many
>threads".
>Maybe that problem has been already fixed but we could not check that.
>Unfortunately nightly builds don't work for now (they even 
>can't perform
>any request from my tests) - we tried 4 last builds (02/05/2004 -
>02/08/2004).
>

I'll try and look at the Regex problem, as I'm sure will others.

==

But as a separate issue - what was the problem with the recent builds?
There have been some test failures that we are aware of (but they are due to
running without a display), but I don't think any of us are aware of any
other major problems.
If there are problems, then we need to amend the unit tests to detect
them...

Which host did you download from?
Have you got any logs (jmeter.log) ?

Note that you need both the _bin (Jmeter binary) and _lib (3rd party jars)
files, which should be unzipped in the same directory tree - i.e. pick the
same top-level directory and unzip preserving folders.

S.


___________________________________________________________________________

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: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org

RE: JMeter from time to time doesn't calculate regular expression s for some threads

[Vladimir Tsygankov <Vl...@contera.sp.ru>]

Regards,
Vladimir

> -----Original Message-----
> From: BAZLEY, Sebastian [mailto:Sebastian.BAZLEY@london.sema.slb.com]
> Sent: Monday, February 09, 2004 9:13 PM
> To: 'JMeter Users List'
> Subject: RE: JMeter from time to time doesn't calculate regular
expression
> s for some threads
> 
> >-----Original Message-----
> >From: Vladimir Tsygankov [mailto:Vladimir@contera.sp.ru]
> >Sent: 09 February 2004 18:02
> >To: 'JMeter Users List'
> >Subject: RE: JMeter from time to time doesn't calculate regular
> >expressions for some threads
> >
> >
> >Hello, colleagues,
> >I'm returning to the problem of "Regular expression problem for many
> >threads".
> >Maybe that problem has been already fixed but we could not check
that.
> >Unfortunately nightly builds don't work for now (they even
> >can't perform
> >any request from my tests) - we tried 4 last builds (02/05/2004 -
> >02/08/2004).
> >
> 
> I'll try and look at the Regex problem, as I'm sure will others.
> 
> ==
> 
> But as a separate issue - what was the problem with the recent builds?
> There have been some test failures that we are aware of (but they are
due
> to
> running without a display), but I don't think any of us are aware of
any
> other major problems.
> If there are problems, then we need to amend the unit tests to detect
> them...
> 
> Which host did you download from?
Latest nightly build we took from
http://gump.covalent.net/jars/latest/jakarta-jmeter/

> Have you got any logs (jmeter.log) ?


when we run our test under the latest build
(jakarta-jmeter-20040208_bin.zip + jakarta-jmeter-20040208_lib.zip) we
get the java.lang.OutOfMemoryError  Exception message in the java
console window.
When we tried to test under previous builds (02/05/2004 - 02/05/2007) we
got jmeter's logs. CSVRead function seems not to work (See log files
attached).
  
> 
> Note that you need both the _bin (Jmeter binary) and _lib (3rd party
jars)
> files, which should be unzipped in the same directory tree - i.e. pick
the
> same top-level directory and unzip preserving folders.
> 
> S.
> 
> 
>
________________________________________________________________________
__
> _
> 
> 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: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> 

Regular expressions for some threads are calculated incorrectly

[Vladimir Tsygankov <Vl...@contera.sp.ru>]

Hello, colleagues,
We think the next regular expression function 
${__regexFunction(<option value="(.*)"
>File,$1$,${__threadNum},,,refContainerID)}
for various threads from time to time works incorrectly in non-GUI
JMeter mode. It misses results for threads.
We attached log files for cases of correct (Thread32-server answer.txt,
Thread32-correct request.txt) and incorrect (Thread33-server answer.txt,
Thread33-incorrect request.txt) working. 
It should work the next way:
for thread 32: ContainerID=47
for thread 33: ContainerID=48 (really ContainerID=49 - it is for another
thread!)

Notes. 1. It happens occasionally (for any thread. Sometimes it doesn’t
happen at all).
2. It seems to depend on number of threads (it doesn't take place for a
few threads). We were 
testing for about 100 threads (users)
3. Perhaps it connected with incorrect function "__threadNum" which is
included in regexFunction.
4. We tried some times under JMeter with GUI and it worked fine.
5. We used JMeter (jakarta-jmeter-20040215).

Thanks in advance,
Vladimir