This is now fixed on GitHub master. Thanks again for reporting!
Lukas
2014-10-29 15:50 GMT+01:00 Lukas Eder lukas.e...@gmail.com:
Hello,
Thanks for reporting this. You're right, there should be some additional
defensiveness around that rollback call - probably logging to the error
logger
Hello,
Thanks for reporting this. You're right, there should be some additional
defensiveness around that rollback call - probably logging to the error
logger and then proceeding with throwing the cause. I've registered an
issue for this, which will be fixed in jOOQ 3.5.0 and 3.4.5:
Hi,
I love that jOOQ has integrated transaction handling now. One of the rough
spots I found however is that when an exception happens during a
transaction and the rollback that jOOQ then tries to perform fails, it'll
'eat' the exception that caused it. I'm not sure why the rollback fails in