Re: [Sqlrelay-discussion] Cursor Error

[Roger <b-r...@ro...>]

On Tue, 28 Jul 2009, David Muse wrote:

> I recently put a fix in CVS that should fix this problem with MySQL.
>
> A patch would be to modify src/connections/mysql/mysqlconnection.C and
> change the openCursor method as follows:
>
> bool mysqlcursor::openCursor(uint16_t id) {
>     stmt=mysql_stmt_init(&mysqlconn->mysql);
>     return sqlrcursor_svr::openCursor(id);
> }
>
> Give that a try, I think it will fix the problem.

	It didn't seem to hurt anything, but it hasn't helped, either.
(You have my sqlrelay.conf file.) The mail instance runs 24/7, and the
hourly "cursor error" files overnight are at least as many retries as
before.

	At least I figured how to add a retry loop, which must disconnect
from sqlrelay and reconnect, but so far, has only required one retry per
incident. But it's still a kludge.

	What is happening that a cursor would not be available?

-- 
Roger