I'll log the bug with RDB, and fix our side as well.
Sorry about this, it is bad exception handling on our side that makes all
of JSR220-ORM not start due to the error in RDB. Can you maybe try some
other database (we tested with MySql and Derby) as a temporary workaround?
Thanks for the detailed info and for supporting JSR220-ORM.