Tomcat setup code#

When you are doing this, make sure the schema is properly setup, or the datastore will list all the tables it can find in the schema it can access. Then, configure the connection parameters so that the JNDI path matches the one specified in the Tomcat configuration: Login into the GeoServer web administration interface and configure the datastore.įirst, choose the Oracle (JNDI) datastore and give it a name:

Tomcat setup code#

LogAbandoned (default false) Flag to log stack traces for application code which abandoned a Statement or Connection.įor more information about the possible parameters and their values refer to the DBCP documentation. RemoveAbandonedTimeout (default 300) Timeout in seconds before an abandoned connection can be removed. Setting this to true can recover db connections from poorly written applications which fail to close a connection. If set to true a connection is considered abandoned and eligible for removal if it has been idle longer than the removeAbandonedTimeout. RemoveAbandoned (default false) Flag to remove abandoned connections if they exceed the removeAbandonedTimout. MinEvictableIdleTimeMillis (default 1000 * 60 * 30) The minimum amount of time an object may sit idle in the pool before it is eligible for eviction by the idle object evictor (if any). NumTestsPerEvictionRun (default 3) The number of objects to examine during each run of the idle object evictor thread (if any). When non-positive, no idle object evictor thread will be run. TimeBetweenEvictionRunsMillis (default -1) The number of milliseconds to sleep between runs of the idle object evictor thread. Other parameters to setup connection pool: Using too low values for removedAbandonedTimeout and minEvictableIdleTimeMillis may result in connection failures, if so try to setup logAbandoned to true and check your catalina.out log file. Modify following settings only if you really know what you are doing. Prepared statement pooling (very important for good performance)Īt most 100 prepared statements in the poolĪ validation query that double checks the connection is still alive before actually using it (this is not necessary if there is guarantee the connections will never drop, either due to the server forcefully closing them, or to network/maintenance issues). The pool configuration shows is quite full-fledged:Īt most 20 active connections (max number of connection that will ever be used in parallel)Īt most 3 connections kept in the pool unused

The example sets up a connection pool connecting to the local Oracle XE instance.