Tomcat oracle driver

I'd recommend upgrading from ojdbc6. I have put the ojdbc7. After a bit of debugging, It seems that tomcat's JreMemoryLeakPreventionListener initializes the DriverManager from the "system" classloader and not the "common" classloader from tomcat's code :.

Since ojbc7. With this, the driver is registered using the service provider mechanism from the JreMemoryLeakPreventionListener invocation using the system classloader. It's a bit complex but the DriverManager itself may cause and additional registration of the driver from the webapp's classloaders when it calls Class.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. How to register oracle jdbc driver on Tomcat 7. Ask Question. Asked 8 years, 1 month ago. Active 6 years, 10 months ago. Viewed 18k times. Improve this question. Add a comment. Active Oldest Votes. Improve this answer. Yes, that's what I meant: the lib folder under Tomcat root. If you use a JNDI data source, and you should, that's where they belong. I had the same issue when trying to use ojdbc7. Sign up or log in Sign up using Google.

For Oracle 9i onwards you should use oracle. OracleDriver rather than oracle. OracleDriver as Oracle have stated that oracle. OracleDriver is deprecated and support for this driver class will be discontinued in the next major release.

In a similar manner to the mysql config above, you will need to define your Datasource in your Context. Here we define a Datasource called myoracle using the thin driver to connect as user scott, password tiger to the sid called mysid. Note: with the thin driver this sid is not the same as the tnsname. The schema used will be the default schema for the user scott. You should ensure that you respect the element ordering defined by the DTD when you create you applications web. You can use the same example application as above assuming you create the required DB instance, tables etc.

This has to be done regardless of which configuration step you take next. You have two choices here: define a datasource that is shared across all Tomcat applications, or define a datasource specifically for one application. Use this option if you wish to define a datasource that is shared across multiple Tomcat applications, or if you just prefer defining your datasource in this file. This author has not had success here, although others have reported so.

Clarification would be appreciated here. Use this option if you wish to define a datasource specific to your application, not visible to other Tomcat applications. This method is less invasive to your Tomcat installation. Create a resource definition for your Context. The Context element should look something like the following. These solutions either utilise a single connection to the database not recommended for anything other than testing!

In order to use OCI driver, you should have an Oracle client installed. You should have installed Oracle8i 8. After renaming classes You may also have to remove the javax.

Ensure that you have the ocijdbc8. You should next create a simple test servlet or JSP that has these critical lines :. The Oracle documentation says : "Cause: The login connect string contains an invalid driver designator.

Action: Correct the string and re-submit. Here are some common problems encountered with a web application which uses a database and tips for how to solve them.

Tomcat runs within a JVM. The JVM periodically performs garbage collection GC to remove java objects which are no longer being used. If the maximum time configured for establishment of a database connection is less than the amount of time garbage collection took you can get a database connection failure. The remainder will only take a few seconds. Rarely, if ever should a GC take more than 10 seconds. Make sure that the db connection timeout is set to seconds.

These can occur when one request gets a db connection from the connection pool and closes it twice. When using a connection pool, closing the connection just returns it to the pool for reuse by another request, it doesn't close the connection. And Tomcat uses multiple threads to handle concurrent requests. Here is an example of the sequence of events which could cause this error in Tomcat:. Here is an example of properly written code to use a database connection obtained from a connection pool:.

Please note that although the above instructions place the JNDI declarations in a Context element, it is possible and sometimes desirable to place these declarations in the GlobalNamingResources section of the server configuration file. A resource placed in the GlobalNamingResources section will be shared among the Contexts of the server. Preventing database connection pool leaks A database connection pool creates and manages a pool of connections to a database. MySQL configuration Ensure that you follow these instructions as variations can cause problems.

Set to -1 for no limit. An Exception is thrown if this timeout is exceeded. Set to -1 to wait indefinitely. Context configuration In a similar manner to the mysql config above, you will need to define your Datasource in your Context. PostgreSQL 0. Resource configuration You have two choices here: define a datasource that is shared across all Tomcat applications, or define a datasource specifically for one application.