JDBC Connection Proxy Across Threads

Has anyone used a wrapper around a JDBC Connection that uses one thread to interact with the calling code, and a separate thread to talk to the database ? Perhaps something similar to jdbc-trace-wrapper (http://code.google.com/p/jdbc-trace-wrapper/ ) but with a greater degree of maturity ?

We've had issues with JDBC calls to 开发者_JAVA技巧particular databases hanging ( never returning ) and this would give us a low-level way to prevent our calling code thread from remaining perpetually blocked, independent of individual JDBC driver implementations ( We've tried Statement.setQueryTimeout(), oracle.jdbc.driver.T4CConnection.abort() etc without reliable success ).