Home/ Questions/Q 6671535
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T03:23:59+00:00

I’m using plain-JDBC-Database-Access in a multithreaded environment. An exception I recently got when working

  • 0

I’m using plain-JDBC-Database-Access in a multithreaded environment.

An exception I recently got when working with PreparedStatements (the Oracle flavour) made me aware of the fact, that they are not threadsafe.

There is, of course, always the possibility to use ThreadLocal-Variables (or synchronize access to the statement), but is there a more clever way to access a database in a multithreaded way?

Edit: To simplify the problem, I’m accessing the database read-only so parallel transactions are no concern to me.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Putting the PreparedStatement into a ThreadLocal into will not solve the problem – even the Connection must be put into ThreadLocal. But then you must make sure, that the connection is also released properly even when exceptions are thrown.

    And what about transactions? How do you make sure, that one transaction does not contain stuff from independent threads?

    The best way would be to adopt some patterns of EJB containers – here the infrastructure takes care of the resource and transaction management and connection pooling. But retrofitting existing code into EJB or even Spring correctly is not an easy task.

    • 0