Opened 9 years ago

Last modified 9 years ago

#25362 closed Uncategorized

psycopg2.InterfaceError is not handled — at Initial Version

Reported by: Amit Prakash Ambasta Owned by: nobody
Component: Database layer (models, ORM) Version: 1.6
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Similar to ticket #21553 psycopg2.InterfaceError is not handled correctly and leads to django re-using the same connection despite it being closed.

StackTrace Below:
Traceback (most recent call last):

File "/home/ubuntu/.virtualenvs/express/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 194, in call

signals.request_started.send(sender=self.class)

File "/home/ubuntu/.virtualenvs/express/local/lib/python2.7/site-packages/django/dispatch/dispatcher.py", line 185, in send

response = receiver(signal=self, sender=sender, named)

File "/home/ubuntu/.virtualenvs/express/local/lib/python2.7/site-packages/django/db/init.py", line 94, in close_old_connections

conn.close_if_unusable_or_obsolete()

File "/home/ubuntu/.virtualenvs/express/local/lib/python2.7/site-packages/django/db/backends/init.py", line 462, in close_if_unusable_or_obsolete

if self.is_usable():

File "/home/ubuntu/.virtualenvs/express/local/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 192, in is_usable

self.connection.cursor().execute("SELECT 1")

psycopg2.InterfaceError: connection already closed

Change History (0)

Note: See TracTickets for help on using tickets.
Back to Top