Tomcat 8.5.29中Oracle数据源配置及数据源注入问题咨询

Hey there, let’s troubleshoot your Tomcat 8.5.29 Oracle Data Source Injection issue step by step. Based on the server.xml snippet you shared, here are the most likely culprits and fixes:

1. Fix the Oracle JDBC Driver Setup #

First, make sure you’ve placed the correct Oracle XA JDBC driver (like ojdbc8.jar for Java 8/Tomcat 8.5) in the $CATALINA_HOME/lib directory. Don’t put it in your web app’s WEB-INF/lib—Tomcat needs the driver at the container level to initialize the data source properly. If the driver is missing or mismatched, you’ll get a ClassNotFoundException for oracle.jdbc.xa.client.OracleXADataSource.

2. Correct the Database URL Format #

Your current URL has a syntax error:

url="jdbc:oracle:thin:<host_name>:1521:<db_name>"

The Oracle thin driver requires an @ symbol after thin:. Fix it to:

url="jdbc:oracle:thin:@<host_name>:1521:<db_name>"

Without this, Tomcat can’t establish a connection to the Oracle database, which breaks data source injection.

3. Update Resource Configuration Properties #

Tomcat 8.5 uses updated connection pool property names (backward-compatible but better to use the new ones for clarity):

• Replace maxActive="100" with maxTotal="100"
• Replace maxWait="10000" with maxWaitMillis="10000"

Also, explicitly specify the data source factory to avoid ambiguity:

factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"

Here’s the corrected Resource snippet for server.xml:

<GlobalNamingResources>
  <Resource 
    name="jdbc/personapp" 
    global="jdbc/personapp" 
    auth="Container" 
    type="javax.sql.DataSource"
    driverClassName="oracle.jdbc.xa.client.OracleXADataSource"
    url="jdbc:oracle:thin:@<host_name>:1521:<db_name>"
    username="my_user_name"
    password="my_pwd"
    maxTotal="100"
    maxIdle="20"
    minIdle="5"
    maxWaitMillis="10000"
    factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
  />
</GlobalNamingResources>

4. Link the Global Data Source to Your Web App #

A global resource in server.xml won’t be accessible to your app unless you create a ResourceLink in either:

• Your app’s META-INF/context.xml, or
• Tomcat’s global conf/context.xml

Add this line to the file:

<ResourceLink name="jdbc/personapp" global="jdbc/personapp" type="javax.sql.DataSource"/>

This maps the global JNDI resource to your app’s local naming context, making it available for injection.

5. Validate Database Credentials and Permissions #

Double-check that:

• The username my_user_name and password my_pwd are correct. Test them with a tool like sqlplus to confirm you can connect to the database.
• The user has sufficient permissions to access the database objects your app needs.

6. Check Tomcat Logs for Exact Errors #

If none of the above fixes work, head to $CATALINA_HOME/logs and look at catalina.out or localhost.log. These logs will contain detailed stack traces that pinpoint the exact issue—whether it’s a driver problem, connection failure, or JNDI lookup error.

If you can share the relevant log snippets, we can narrow it down even further!

内容的提问来源于stack exchange，提问作者Sumit Ghosh