title: Deal with deadlocks in MySQL/InnoDB
body: <p>I'm benchmarking MySQL under different isolation levels.</p>
  
  <p>For the case of SERIALIZABLE I frequently get this error: <code>"Deadlock found when trying to get lock; try restarting transaction at the client side"</code>.</p>
  
  <p>Reading <a href="http://dev.mysql.com/doc/refman/5.6/en/innodb-deadlocks.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.6/en/innodb-deadlocks.html</a> didn't help me much.</p>
  
  <p>I have the following question:
  What is the state of the database whenever I get the message ? Everything is frozen and the system expects from me to do something or my transaction has been already aborted and I just get informed about it ?</p>
  
  <p>I'm using jdbc driver to connect to MySQL. Supposed my policy is to re-issue such failing transactions, do I need to call <code>connection.rollback()</code> or MySQL has already done that for me ?</p>