Description of problem:
Moving from RH5 (mysql-server-5.0.77-4.el5_5.5) to RH6 (mysql-server-5.1.52-1.el6_0.1.x86_64), mysql-server exhibits a new failure mode (with the InnoDB engine, autocommitting statements, from JDBC)
From time to time, one gets a statement failure
"Table 't' was not locked with LOCK TABLES"
which does not make sense front, back and center as the table in question is clearly not to be meant to be locked with LOCK TABLES.
Similar problems found on net:
This problem was not found on 5.0.77 even for months of operation.
Version-Release number of selected component (if applicable):
Every few hours on a MySQL database under load.
No further information as of yet.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
Without a reproducible test case (preferably, more reproducible than "every few hours") there is absolutely nothing I can do with this report.
Unfortunately I do not have access to the magic test case generator.
Will append more if I know more.
Well, it's premature to file a bug when you don't have adequate evidence. Please either reopen or file a new bug when you do.