On Wed, Nov 9, 2011 at 10:57 PM, Stuart Bishop
<email address hidden> wrote:
> 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.
So, I guess we need to fix the oops. Is this perhaps logged after the
request is 'finished' (which wipes the oops metadata?)
On Wed, Nov 9, 2011 at 10:57 PM, Stuart Bishop
<email address hidden> wrote:
> 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.
So, I guess we need to fix the oops. Is this perhaps logged after the
request is 'finished' (which wipes the oops metadata?)