Comment 6 for bug 44032
Revision history for this message
| Steve Alexander (stevea) wrote Re: Possible use of more than one connection ID on a single thread may be the cause of many OOPSes | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I don't think OOPS-170D339 has the problem. Although the connection id in the traceback is different from that in the statement log, I think this is due to the bug where connection id was used for the statement log, but the cursor id used elsewhere.
This bug has now been fixed in production.
The connection ids in the statement log in this oops report are all the same connection.