Re: MySQL lock time out exceeds, restart the transaction

[Peter Brawley]

> Could you please provide the appropriate tool

Eh? You said it's one transaction. If that's so, then inside the transaction write code to set @mysql variables at relevant points to track the time, and log those values so you can see where the time is spent.

In general, in a busy multi-user environment any transaction can deadlock and any complex transaction can run past a given timeout setting, so all transactions for such environments should be coded to detect deadlocks and timeouts and restart themselves.