Charles, it's not just ignoring the error, it's most of all continuing testing:
without the patch, sipp gives an error message and stops (simulation over, restarting sipp needed; in my case 1000 registration sessions in parallel are all stopped, not just that one call/session) with the patch, you get the error message and the simulation/program continues. You can decide in the script what to do for the session (e.g. test presence with regex and fail the call/session). I think sipp should continue simulation of its sessions, even if some responses from the SUT are wrong/unexpected, as it does most of the time. It is nice to have error indications that such errors occur, but if you stop simulating at the first error you can never drive a system to its limits. Before I had the patch, I spend half a day restarting sipp sessions, that nicely died as soon as load was high enough and the SUT generated one wrong response. Best regards, MarcVD -----Original Message----- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: 05 March 2008 13:49 To: VAN DIEST Marcus (ITN/NIS) Cc: [email protected]; [EMAIL PROTECTED] Subject: Re: [Sipp-users] patch on sipp 3.0 for missing authentication in 401/407 message I'm not sure I like just ignoring this type of error. Maybe you can make it a command line option, or at the very least fail the call? Charles [EMAIL PROTECTED] wrote on 03/05/2008 05:13:55 AM: > Hello all, > I'm sending this mail to the sipp user list as apparently there is not > much life on sipp-devel. > OK, maybe my mistake, I just checked http://sipp.sourceforge. > net/doc/reference.html telling this sipp-users list is the right one, > so here is the mail again anyhow: > From: VAN DIEST Marcus (ITN/NIS) > Sent: 13 February 2008 09:54 > To: '[EMAIL PROTECTED]' > Cc: '[EMAIL PROTECTED]' > Subject: patch on sipp 3.0 for missing authentication in 401/407 > Hello all, > a bug in our system revealed that when sipp receives a 401 without an > Authentication line in the header (recv auth=true), the program quits > with the message "Couldn't find 'Proxy-Authenticate' or 'WWW- > Authenticate' in 401 or 407!". This way, the load on the system is of > course reduced and unstable as the sipp executables disappear on the > first error. > Below you can find a patch that will keep the error messages, but > continues the sipp program execution (sending out the next message > with the [authentication ...] line removed as no auth info was found > in the 401). This way the system load is stable, the errors can still > be found in the xxx_errors.log. > > Best regards, > MarcVD > P.S. can you give a little feedback when treated > (-: from Marc VAN DIEST (BELGACOM) ;-) > ------------------------------------------------------------------------ - > This SF.net email is sponsored by: Microsoft Defy all challenges. > Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
