Is java.sql.Connection thread safe?

java multithreading jdbc thread-safety dbconnection
Boris Pavlović picture Boris Pavlović · Oct 7, 2009 · Viewed 46.1k times · Source

To rephrase the question: should I avoid sharing instances of classes which implement java.sql.Connection between different threads?

Answer

skaffman picture skaffman · Oct 7, 2009

If the JDBC driver is spec-compliant, then technically yes, the object is thread-safe, but you should avoid sharing connections between threads, since the activity on the connection will mean that only one thread will be able to do anything at a time.

You should use a connection pool (like Apache Commons DBCP) to ensure that each thread gets its own connection.

Related questions

Is it safe to use a static java.sql.Connection instance in a multithreaded system?

I'm running a web application on Tomcat. I have a class that handles all DB queries. This class contains the Connection object and methods that returns query results. This is the connection object: private static Connection conn = null; It has …

Read More
Difference between wait() and sleep()

What is the difference between a wait() and sleep() in Threads? Is my understanding that a wait()-ing Thread is still in running mode and uses CPU cycles but a sleep()-ing does not consume any CPU cycles correct? Why …

Read More
"implements Runnable" vs "extends Thread" in Java

From what time I've spent with threads in Java, I've found these two ways to write threads: With implements Runnable: public class MyRunnable implements Runnable { public void run() { //Code } } //Started with a "new Thread(new MyRunnable()).start()" call Or, with …

Read More