#11015: django-1.0.2 does not catch the exception that database backend first
close
the db connection.
---------------------------------------------------+------------------------
Reporter: qingran | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: duplicate | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by adamnelson):
I agree with gkulewski. Is it in Django's ticket policy to close tickets
that are confirmed problems for multiple people just because
reproducibility hasn't been found yet? Django is no longer small enough
to kill bugs just because the reporter doesn't have enough information to
take the ticket to approval level.
I no longer have an Nginx setup, so I can't test this anymore and can't
follow the ticket anymore. However, it was definitely a problem for 2
people on a well-defined environment and has been seen by many people in
the wild:
http://www.google.com/search?hl=en&q=django+connection+already+closed"+while+reading+response+header+from+upstream&aq=f&aqi=&aql=&oq=
With that said, I'm pretty confident that this is a FastCGI problem either
on Django's side or Nginx's - probably Nginx.
--
Ticket URL: <http://code.djangoproject.com/ticket/11015#comment:13>
Django <http://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-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
