InterfaceError: connection already closed should be converted into DisconnectionError
Bug #374909 reported by
Francis J. Lacoste
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Storm |
Fix Released
|
High
|
James Henstridge | ||
Bug Description
Like bug 360846 showed it's possible for disconnection error to go unnoticed and leave the connection in a irrecuperable state. When the connection is in this state, psycopg2 will raise an InterfaceError: connection already closed error, these should be recognized as disconnection error and converted to the appropriate exception.
Related branches
lp://staging/~jamesh/storm/bug-374909
- Stuart Bishop (community): Approve
- Thomas Herve (community): Approve
- Diff: 123 lines
lp://staging/~salgado/storm/bug-374909
- James Henstridge: Approve
- Jamu Kakar (community): Approve
- Diff: 108 lines
Revision history for this message
| James Henstridge (jamesh) wrote | #1 |
| Changed in storm: | |
| assignee: | nobody → James Henstridge (jamesh) |
| importance: | Undecided → High |
| status: | New → Triaged |
| milestone: | none → 0.15 |
| Changed in storm: | |
| status: | Triaged → In Progress |
Revision history for this message
| Thomas Herve (therve) wrote | #2 |
Revision history for this message
| James Henstridge (jamesh) wrote | #3 |
| Changed in storm: | |
| status: | In Progress → Fix Committed |
| Changed in storm: | |
| status: | Fix Committed → Triaged |
Revision history for this message
| Guilherme Salgado (salgado) wrote | #4 |
Revision history for this message
| James Henstridge (jamesh) wrote | #5 |
| Changed in storm: | |
| status: | Triaged → Fix Committed |
| Changed in storm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is affecting U1 too (the Django integration bypasses Storm's disconnection checking, so it is possible for this error to occur).