title: Connection Pooling over New Connection instance per Thread (JDBC)
body: <p>I am creating a multi-threaded application. However, I have experienced lots of unexpected behavior from my application when I have one connection object serving all threads. </p>
  
  <p>I am in a dilemma. Should I let every thread create, use and dispose its own connection object or should I use a connection pool?</p>
  
  <p>I have tried connection pooling which makes the application painfully shower. However, my intuition is that if I let every thread create its own connection object, I might get a "too many connection" error.</p>
  
  <p>Please let me know if there is any way to assist in this.</p>
  
  <p>Regards.</p>