Just as an FYI to anyone out there struggling with this same issue: I was able
to work around this by embedding an extra line that sends a dummy "log mssage"
to stdout in the <action> sections as follows:
<recv response="200">
<action>
<ereg regexp=".*" search_in="hdr" header="Contact:" check_it="false"
assign_to="dummy1"/>
<log message="IGNORE: [$dummy1]"/>
</action>
</recv>
Unfortunately, this breaks any backwards compatibility with my old 2.0.1
executable. If these modified scripts are run against old 2.0.1 sipp, I get a
Segmentation Fault.
Anyway, just an update. My original question remains: Is it really necessary
for sipp to check variable usage?
Jeffrey Wright
System Test Engineering Manager
Aztek Networks, Inc.
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Jeff Wright
Sent: Mon 8/18/2008 10:29 AM
To: [email protected]
Subject: [Sipp-users] Error message: "Variable is referenced 1 times!"
Since migrating to sipp 3.1 (from sipp 2.0.1), the old scenario files that used
to work for me now don't. I get the telltale "VAriable referenced 1 times!"
error message and the script terminates.
I looked through this mail list's archives and discovered that there were
checks put into place that cause this error when a assign_to is made w/o using
the assigned variable later on. Unfortunately, I think there's a flaw of logic
here, because if I remove the assign_to statement for the supposedly offending
variable, sipp then complains that I have to use an assign_to for my regexp!
First, I run *with* the assign_to in place:
<recv request="INFO">
<action>
<ereg regexp="tag=[^;]+" search_in="hdr" header="To:" check_it="true"
assign_to="dummy1"/>
<ereg regexp="tag=[^;]+" search_in="hdr" header="From:" check_it="true"
assign_to="dummy2"/>
</action>
</recv>
which results in:
"sipp 172.22.20.55 -sf successful_call.xml -inf clients.csv -l 1 -i
172.22.20.186 -p 5063 -m 1 2008-08-18 10:21:22:392 1219076482.392181:
Variable $dummy1 is referenced 1 times!"
Then I remove the assign_to:
<recv request="INFO">
<action>
<ereg regexp="tag=[^;]+" search_in="hdr" header="To:" check_it="true"/>
<ereg regexp="tag=[^;]+" search_in="hdr" header="From:" check_it="true"
assign_to="dummy2"/>
</action>
</recv>
and this results in:
"sipp 172.22.20.55 -sf successful_call.xml -inf clients.csv -l 1 -i
172.22.20.186 -p 5063 -m 1
2008-08-18 10:22:03:021 1219076523.021795: assign_to value is missing."
I *need* to have that assign_to in there to allow me to do the check_it on the
To: field. Otherwise my test is compromised (I could conceivably get a INFO
that doesn't have a To: field in it).
I think this is a bug. Is it really necessary for sipp to check my variable
usage?? It breaks my existing scenarios.
Jeffrey Wright
System Test Engineering Manager
Aztek Networks, Inc.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
