Performance bug with JDBC/sqlite driver under multi-threaded conditions

[headius]

This is transferred from jruby/jruby#3398 by @chuckremes.

The original issue seems to be that the jdbc-sqlite3 driver is compiled with a very conservative threading model, which prevents even isolated databases from being accessed concurrently. After some discussion, @patcheng figured out the right combination of build flags to be safe but still fast. We will work with @xerial via xerial/sqlite-jdbc#59 to get a release out, and then we'll need to release an update for the jdbc-sqlite3 gem.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/35052822-performance-bug-with-jdbc-sqlite-driver-under-multi-threaded-conditions?utm_campaign=plugin&utm_content=tracker%2F136963&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F136963&utm_medium=issues&utm_source=github).

[kares]

seems it got accepted by sqlite-jdbc ... will be waiting for 3.13 to take it for a spin