Looks like a bug on the database end where it's stuck in a loop where the last transaction is contantly getting rolled back and transactions are being done all over again.
Yes, that is correct. Mark said on irc last time that it was a db rollback. Looks like he didn't bother getting the cause fixed.