Comment 14 for bug 504291

The code is already there to reset the store to a working state, done straight after logging the OOPS:

                # The Store is in a disconnected state. This should
                # not happen, as store.rollback() should have been called
                # by now. Log an OOPS so we know about this. This
                # is Bug #504291 happening.
                getUtility(IErrorReportingUtility).raising(
                    sys.exc_info(), request)
                # Repair things so the server can remain operational.
                store.rollback()

I'm not sure how to proceed on this. At the end of the request, we are detecting the invalid state and logging an OOPS. This OOPS (such as OOPS-2077A100) is empty, containing no call traces or information on how this request managed to screw up the database connection.