#19022: Connection reset by peer with development server.
-------------------------------+--------------------
Reporter: tdhutt@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.4
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
When running the development server both with and without --nothreading,
sometimes we get connection reset by peer errors. We are using Chrome and
not sending any POST or GET parameters, and it works most of the time. It
seems to be when there are lots of connections in a row or concurrent
connections that it has issues. Clearly it should be able to handle that
without resetting the connection, even if it only processes the requests
serially. There's no reason it shouldn't work when running multithreaded
either.
There are various other bugs in the database related to this, but they all
appear to be closed or marked as duplicates of unrelated bugs and this is
still an issue. See especially #18126.
--
Ticket URL: <https://code.djangoproject.com/ticket/19022>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
