Ticket Navigation

Ticket #184 (defect)

Opened 3 years ago

Last modified 3 years ago

tutorial01 errorlogs on ab benchmark

Status: closed (fixed)

Reported by:	slate	Assigned to:	rdelon
Priority:	high	Milestone:	2.1
Component:	CherryPy code	Keywords:	wsgi requestline
Cc:

cherrypy svn revision 298

python version 2.3.4

OS=linux

export PYTHONPATH=/home/bd/Projektek/cherrysvn/trunk/

All test ran OK.

I started: tut01_helloworld.py

I tried: ab -n 100 -c 8 localhost:8080/

Result in cherrypy log:

Traceback (most recent call last):
  File "/home/bd/Projektek/cherrysvn/trunk/cherrypy/_cpwsgiserver.py", line 144, in run
    request.parse_request()
  File "/home/bd/Projektek/cherrysvn/trunk/cherrypy/_cpwsgiserver.py", line 66, in parse_request
    method,path,version = request_line.strip().split(" ", 2)
ValueError: unpack list of wrong size
Traceback (most recent call last):
  File "/home/bd/Projektek/cherrysvn/trunk/cherrypy/_cpwsgiserver.py", line 148, in run
    request.write(line)
  File "/home/bd/Projektek/cherrysvn/trunk/cherrypy/_cpwsgiserver.py", line 109, in write
    self.wfile.flush()
  File "/usr/lib/python2.3/socket.py", line 241, in flush
    self._sock.sendall(buffer)
error: (32, 'Broken pipe')
2005/06/12 23:25:13 HTTP INFO 127.0.0.1 - GET / HTTP/1
Traceback (most recent call last):
  File "/home/bd/Projektek/cherrysvn/trunk/cherrypy/_cpwsgiserver.py", line 148, in run
    request.write(line)
  File "/home/bd/Projektek/cherrysvn/trunk/cherrypy/_cpwsgiserver.py", line 109, in write
    self.wfile.flush()
  File "/usr/lib/python2.3/socket.py", line 241, in flush
    self._sock.sendall(buffer)
error: (32, 'Broken pipe')

last TraceBack? repeated several times

Change History

06/12/05 17:23:35: Modified by peterhunt

i dont have a linux box so i dont get this error can someone plz catch this exception and ignore it? everyone asks about it.

06/12/05 17:29:01: Modified by peterhunt

i dont have a linux box so i dont get this error can someone plz catch this exception and ignore it? everyone asks about it.

06/22/05 00:58:00: Modified by fumanchu

This problem still exists in revision [357]. First 106 requests work, but the next one fails, since requestLine at that point is "".

06/22/05 02:02:43: Modified by fumanchu

keywords set to wsgi requestline.
status changed from new to closed.
resolution set to fixed.
milestone set to 2.1.

Fixed in changeset [358]. Not sure why. The critical line is the new "self.ready = False" when requestLine is "", but how any request could be in a state where self.ready is True at that point is beyond me. Somehow, the same request must be put on the queue more than once? Funky.