<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:10pt"><div>(If anyone gets this twice, apology in advance. I think I jumped the gun in sending the email before I got my acknowledge welcome email for the list.)<br><br>It looks like the latest version 8.2 tries to rollback without seeing if the connection is even open or not:<br><br> def rollback(self):<br> if not self._pool.reconnect:<br> self._connection.rollback()<br> return<br><br> try:<br> self._connection.rollback()<br> curs =
self._connection.cursor()<br>
curs.execute(self._pool.good_sql)<br> curs.close()<br> self._connection.commit()<br> return<br> except:<br> log.err(None, "<span style="border-bottom: 1px dashed rgb(0, 102, 204); cursor: pointer;" class="yshortcuts" id="lw_1241118141_0">Rollback</span> failed")<br><br> self._pool.disconnect(self._connection)<br><br> if self._pool.noisy:<br> log.msg("Connection lost.")<br><br> raise ConnectionLost()<br><br>I'm
seeing the "Rollback failed" log message and then the ConnectionLost
exception being thrown. I have cp_reconnect set to True, so it's
skipping down to the try/except and failing on rollback. Should the
code try to rollback if the connection is lost?<br><br>Thanks in advance,<br>Steve</div></div><br>
</body></html>