Tomcat sql server driver

This makes the driver available to JDBC. Note: if you've read instructions that talk about Classpath , just ignore them - they're not applicable to recent versions of Tomcat. The Java Servlet specification that Tomcat implements requires resources to be declared in two places:. The Resource Element defines server-specific information about your database, including URL, database type , driver, and authentication information. As mentioned above, there are two ways to define this information - as a GlobalNamingResource, if multiple Contexts will need access to a single database, or on a Context by Context basis.

As the second of these is the more common usage, let's look at that first. If you'll need to use a GlobalNamingResource, click here to skip ahead. All actively supported versions of Tomcat allow configuration of Contexts through either an entry in Server. We strongly recommend you use the second option, as this will allow you to make changes to your database configuration without restarting your entire server, and also make your application more portable.

You can find more information on determining the proper connection pooling attributes later in this article. It is nested inside the Context element. Replace the [placeholders] with the proper values for your server. For most users, there should be no need to modify the "type", "driverClassName", or "auth" attributes:. If you will be accessing a globally declared JDBC resource, as outlined in the next section , use a ResourceLink entry in place of the Resource element, as in the example below:.

The "name" attribute allows you to define a per-Context name for the resource, that can be used in your application code, as long as the "global" value correctly identifies the referenced resource. ResourceLink elements can also be defined on a per-host basis, and referenced via web.

Isn't flexibility great? If you want a single database to be accessible to multiple Contexts, you can define it in server.

Here is a sample GlobalNamingResources configuration. The only major difference between this example and the per-Context configuration is its location:. Now that you've configured the main Resource entry, it's time to provide Resource Reference information, which will make your application more portable. That's it! Like all pooling implementations, connection pooling can cause a few annoying problems if it is not configured correctly. Here are a few common connection pooling issues and how to fix them.

In addition to allowing the driver to acquire Kerberos credentials using the settings specified in the login module configuration file, the driver can use existing credentials. This can be useful when your application needs to create connections using more than one user's credentials. The driver will attempt to use existing credentials if they are available, before attempting to login using the specified login module. Thus, when using the Subject. For more information about Kerberos configuration files, see Kerberos Requirements.

You can enable a domain configuration file with -Djava. You can enable a login module configuration file with -Djava. The delegated credential can be passed in as org. GSSCredential object, these credentials are used by driver to establish connection. This guide assumes a working Kerberos setup already exists.

Run the following code on a Windows machine with working Kerberos authentication to verify if the aforementioned is true. No additional run-time flags, dependencies, or driver settings are required outside of the ones provided. The same block of code can be run on Linux to verify successful connections. Skip to main content. This browser is no longer supported. The pool itself doesn't timeout the query, it is still up to the JDBC driver to enforce query timeouts.

A value less than or equal to zero will disable this feature. String The name of a class which implements the org. Validator interface and provides a no-arg constructor may be implicit. If specified, the class will be used to create a Validator instance which is then used instead of any validation query to validate connections.

An example value is com. This value should not be set under 1 second. It dictates how often we check for idle, abandoned connections, and how often we validate idle connections. This value will be overridden by maxAge if the latter is non-zero and lower. The default value is 5 seconds. The default value is 60 seconds. Access can be achieved by calling unwrap on the pooled connection.

DataSource interface, or call getConnection through reflection or cast the object as javax. If set to true a connection is considered abandoned and eligible for removal if it has been in use longer than the removeAbandonedTimeout Setting this to true can recover db connections from applications that fail to close a connection.

See also logAbandoned The default value is false. The default value is 60 60 seconds. The value should be set to the longest running query your applications might have.

Logging of abandoned Connections adds overhead for every Connection borrow because a stack trace has to be generated. String The connection properties that will be sent to our JDBC driver when establishing new connections. String A custom query to be run when a connection is first created. String A semicolon separated list of classnames extending org. JdbcInterceptor class. These interceptors will be inserted as an interceptor into the chain of operations on a java. Connection object.

Predefined interceptors: org. ConnectionState - keeps track of auto commit, read only, catalog and transaction isolation level. StatementFinalizer - keeps track of opened statements, and closes them when the connection is returned to the pool.

If a connection is due for validation, but has been validated previously within this interval, it will not be validated again. The default value is 3 seconds. This uses the org. FairBlockingQueue implementation for the list of the idle connections. The default value is true. This flag is required when you want to use asynchronous connection retrieval. Setting this flag ensures that threads receive connections in the order they arrive.

During performance tests, there is a very large difference in how locks and lock waiting is implemented. If the system is running on Linux property os. To disable this Linux specific behavior and still use the fair queue, simply add the property org. The value should be between The default value is 0 , which implies that connections are eligible for closure as soon as removeAbandonedTimeout has been reached. The default value is 0 , which implies that connections will be left open and no age check will be done upon borrowing from the pool, returning the connection to the pool or when checking idle connections.

This property does not apply to added interceptors as those are configured individually. Default value is 0. Similar to to the removeAbandonedTimeout value but instead of treating the connection as abandoned, and potentially closing the connection, this simply logs the warning if logAbandoned is set to true.

If this value is equal or less than 0, no suspect checking will be performed. Suspect checking only takes place if the timeout value is larger than 0 and the connection was not abandoned or if abandon check is disabled. The pool can however be configured to allow use of different credentials each time a connection is requested.

To enable the functionality described in the DataSource. This way, the pool size is still managed on a global level, and not on a per schema level.

This property was added as an enhancement to bug DataSource Inject a data source to the connection pool, and the pool will use the data source to retrieve connections instead of establishing them using the java. Driver interface. This is useful when you wish to pool XA connections or connections established using a data source instead of a connection string. Default value is null.

See the dataSource attribute. This prevents a thread holding on to a reference of a connection it has already called closed on, to execute queries on it. Default value is true. Default value is false for backwards compatibility. Set to true if you want to ignore error of connection creation while initializing the pool. Set to false if you want to fail the initialization of the pool by throwing exception. To see an example of how to use an interceptor, take a look at org.

This simple interceptor is a cache of three attributes, transaction isolation level, auto commit and read only state, in order for the system to avoid not needed roundtrips to the database.

Further interceptors will be added to the core of the pool as the need arises. Contributions are always welcome! Interceptors are of course not limited to just java. Connection but can be used to wrap any of the results from a method invocation as well. You could build query performance analyzer that provides JMX notifications when a query is running longer than the expected time.

The property contains a list of semicolon separated class names. If the classname is not fully qualified it will be prefixed with the org. ConnectionState; org. Interceptors can have properties as well. Properties for an interceptor are specified within parentheses after the class name. Several properties are separated by commas.

Caches the connection for the following attributes autoCommit , readOnly , transactionIsolation and catalog. It is a performance enhancement to avoid roundtrip to the database when getters are called or setters are called with an already set value. Keeps track of all statements created using createStatement , prepareStatement or prepareCall and closes these statements when the connection is returned to the pool.

When enabled and a connection is closed, and statements are not closed, the interceptor will log all stack traces. The statements are cached per connection.

The count limit is counted globally for all connections that belong to the same pool. Once the count reaches max , subsequent statements are not returned to the cache and are closed immediately. See Interceptor to wrap statements and result sets in order to prevent access to the actual connection using the methods ResultSet. Automatically calls java. The default value is 1 seconds. Keeps track of query performance and issues log entries when queries exceed a time threshold of fail.

The log level used is WARN. The default value is milliseconds. A value less than or equal to 0 will disable this feature. Extends the SlowQueryReport and in addition to log entries it issues JMX notification for monitoring tools to react to.

Inherits all the attributes from its parent class. String Define a valid javax.