- Date: 7 March 2007
- Versions affected: 1.x
When examining the transaction logs, Log Rescue may throw a timeout exception. Once possible cause is that there is an uncommitted transaction currently running against your database. In this case, Log Rescue will continue waiting for the transaction to complete before returning results. If an improperly-formed transaction has begun on the database which never completes, Log Rescue may wait until the timeout period has elapsed before displaying a query timeout exception.
Note that this information does not apply if the timeout is occurring at any other stage of processing, such as reading backup history. This only applies to timeouts which occur while reading the transaction log from the server.