it is hard to track down the cause of "ConnectionError: txn created while DB pool shutting down" errors
exarkun@… originally submitted this as ticket:836
This error happens when ConnectionPool.connection is called after ConnectionPool.stopService is called. No new connections are allowed when the pool is stopping (or stopped).
This exception doesn't come with a traceback or even a connection label. If a unit test trips over it, it just looks like:
[ERROR]
Traceback (most recent call last):
Failure: twext.enterprise.ienterprise.ConnectionError: txn created while DB pool shutting down
A stack trace for the place where connection was called to trigger this would be pretty cool. A smaller change would be including the connection label in the exception message: at least this would let an application make this unambiguous (by using labels the developer knows how to track back to code).
@wsanchez originally submitted this as comment:1:ticket:836
- Priority changed from 4: Nice to have to 3: Important
- Milestone set to Later