[httperf] how to treat reply status 500 as error?

[Arlitt, Martin]

Hi Kevin

I don't think there is a way to do this without modifying the code.  If you want to attempt this, take a look at gen/session.c, and search for failure_status; this will show you how the error is generated in session-based workloads.  For request-based workloads, you would likely need to edit http.c (e.g., where the status line or the response is parsed) or perhaps in core.c.  Since you already have a Web server generating status 500 errors, it should be straightforward for you to test.

Thanks

Martin


> -----Original Message-----
> From: httperf-bounces at napali.hpl.hp.com [mailto:httperf-
> bounces at napali.hpl.hp.com] On Behalf Of Kevin Kettinger
> Sent: Sunday, May 17, 2009 7:14 AM
> To: httperf at napali.hpl.hp.com
> Subject: [httperf] how to treat reply status 500 as error?
> 
> hi,
> 
> i realy like httperf and currently i am benchmarking lighttpd + fcgi +
> php.
> 
> i know there is --failure-status but this is just for session based
> benchmarking so i cant use it.
> 
> the problem is, that lighttpd throws an http 500 error code when the
> fcgi backend is overloaded and this should be treated as an error.
> 
> is there any other possibilities to treat some reply status as error in
> a request based benchmark?
> 
> thanks.
> 
> regards,
> kevin :-)
> _______________________________________________
> httperf mailing list
> httperf at linux.hpl.hp.com
> http://www.hpl.hp.com/hosted/linux/mail-archives/httperf/