SQL for Confluence data source configuration - 8.x

Archive

This page has been replaced by Configure application server based data sources and Data source configuration - problem determination. Some of the information is out of date with respect to new releases of the app. However, we have kept the page as it has comments and answers that may still be helpful.

Summary

SQL for Confluence uses data sources defined to the application server to gain access to the database. The data source is referenced using the dataSource parameter. The exact configuration of a data source is application server and database specific. The configuration must be done by a Confluence administrator and the Confluence application server must be restarted for changes to be active. The configuration must be done very carefully as any errors results in the data source being unusable (sad). Each database you need to access in Confluence must a have a data source configuration.

These are the major elements of the configuration:

  1. Application server data source configuration - consult your application server documentation on how this is done and problem determination mechanisms. Note that the configuration may be specific to the application server version. For example, older Tomcat versions have some different configurations.
  2. JDBC driver specific for the database to be accessed - consult your database documentation and other sources for the best JDBC driver to use.
  3. Installation of JDBC driver on the application server.
  4. Database access - consult your database documentation on how to configure your database for access.

Various users have provided some examples that cover many standard situations. This page can be used to share that type of information as well as problem determination information. This is the best place to start especially if you are not an expert in this area.

Just upgraded Confluence?

A common problem is errors after upgrading Confluence. Ensure that your upgrade procedures include updating your server.xml and copying all the JDBC drivers you use into the appropriate location. Also, check out this page for isolating these or application server version differences that cause problems. If you get errors immediately after an upgrade, this is the most likely cause.


Confluence standalone installation (Tomcat)

Many users install the standard Confluence standalone distribution. This section discusses configuration specific to this application server environment. The most recent versions of Confluence use newer versions of the Tomcat application server where the following configuration examples apply:

JDBC driver location

Put the driver jar in <install-dir>/lib - this is the directory that has other Tomcat jars. If you have an older version of Confluence that does not have this directory, look for <install-dir>/common/lib instead.

Tomcat configuration

Modify <install-dir>/conf/server.xml to add one or more data source resource elements. User's Guide is an example of adding a few data sources for various local and non-local databases.

The essential element is something like the following, where the data source name is myDS:

<Resource name="jdbc/myDS"
    auth="Container" 
    type="javax.sql.DataSource" 
    username="confluence" 
    password="confluence"
    maxActive="100"
    maxIdle="10"
    driverClassName="org.postgresql.Driver"
    url="jdbc:postgresql://localhost:5432/mydatabase"
    validationQuery="Select 1"
/>

Resource must be within the Confluence context tag

...
<Context path="" docBase="../confluence" debug="0" reloadable="false">
...
<Resource ... />
...
</Context>


Database examples

The sql macro markup looks like: {sql:datasource=myDS| ... }

Other databases

Support for other databases depends on the capabilities provided by the JDBC driver. The SQL for Confluence expects certain JDBC features to be available. In some cases, parameter choices can affect which capabilities are needed. User testing and community support is about the only help that is available for less popular databases/JDBC drivers. If you have had success with other databases, please add information to this page.


WebLogic 9.1 application server

  1. In the WebLogic console, under Services > JDBC, create a data source (see WebLogic's documentation on how to Configure JDBC data sources for more information).
  2. Take note of the JNDI name you used to create the data source.
  3. Point the SQL macro to that JNDI name (dataSource parameter).

Problem determination

Here are some common errors and examples.

  1. Double check all the configuration values and that JDBC driver is installed - use the information above.
  2. Make sure you restarted Confluence after making configuration changes.
  3. Make sure your database is configured from remote access from the Confluence server with the user and password provided. If you have problems, connect using an independent SQL client from the server to verify access. Consult your database documentation for how to configure remote access and database permissions.

Error - no JDBC driver

  • Check your driver location. The driver must be installed in a location that is on the classpath of your application server. For standalone installations, the location is <install-directory>/lib.

    sql: Unexpected program error: com.atlassian.renderer.v2.macro.MacroException: 
    org.apache.tomcat.dbcp.dbcp.SQLNestedException: 
    Cannot load JDBC driver class 'net.sourceforge.jtds.jdbc.Driver'
    

Error - database server not found

  • Check your application server (server.xml) configuration and ensure the DNS host name is valid on the server running Confluence.

    sql: Unexpected program error: com.atlassian.renderer.v2.macro.MacroException:
     org.apache.tomcat.dbcp.dbcp.SQLNestedException:
     Cannot create PoolableConnectionFactory (Unknown server host name 'myserver'.)
    

Error - port

  • The database may not be listening on the requested port - verify the port configuration in server.xml and database.

    sql: Unexpected program error: com.atlassian.renderer.v2.macro.MacroException:
     org.apache.tomcat.dbcp.dbcp.SQLNestedException:
     Cannot create PoolableConnectionFactory (Network error IOException: Connection refused)
    

Error - user authentication

  • Application server configuration (server.xml) has the wrong password.

    sql: Unexpected program error: com.atlassian.renderer.v2.macro.MacroException:
     org.apache.tomcat.dbcp.dbcp.SQLNestedException:
     Cannot create PoolableConnectionFactory (FATAL: password authentication failed for user "bad")
    

Error - validation query

  • Validation query not supported or incorrect syntax - remove the validation query or ensure it is correct for your database.

    sql: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Syntax error: Encountered "<EOF>" at line 1, column 8.)
    

Error - user authority

  • User does not have permission to the database or table - modify your database configuration.

    sql: org.postgresql.util.PSQLException: ERROR: permission denied for relation test01
    

Error - bad server.xml configuration

  • The resource configuration is outside of the confluence context - change your application server configuration (server.xml) to ensure the resource is within the Confluence context.

    sql: Unexpected program error: com.atlassian.renderer.v2.macro.MacroException:
    org.apache.tomcat.dbcp.dbcp.SQLNestedException: 
    Cannot create JDBC driver of class '' for connect URL 'null' 
    

Error - class not found

  • After upgrading Confluence or your application server, this error can occur if your data source configuration is out of date. Look for something like factory="org.apache.commons.dbcp.BasicDataSourceFactory" in your server.xml. Either remove it or rename it to factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory". Reference is SQL-68.

    java.lang.ClassNotFoundException: org.apache.commons.dbcp.BasicDataSourceFactory
    

Error - Cannot create PoolableConnectionFactory (Could not create connection to database server. Attempted reconnect 3 times. Giving up.)

  • Make sure your database server is accepting connections from the Confluence server TCP address and the user is authorized to connect.

Error - MyDS not found

  • The datasource names are case sensitive, make sure you use exactly the same name as what you have configured!

Non-standard JDBC drivers

If you are using a non-standard JDBC driver for accessing less common databases, there are potential problems with unsupported or non-standard behavior. Experiment on a test instance to ensure it works as expected. Here are some workarounds for problems you might encounter. If you continue to have problems, you may need to debug the code on your installation.

  1. Hangs - SQL-86 is an example. Use multipleResults=false to disable multiple results sets.
  2. Avoid using horizontal rowOrientation.

Broken database connections - java.sql.SQLRecoverableException

Add a validation query to your configuration. This helps the application server connection pool to recover from database connection problems.

validationQuery="Select 1"

Other errors

For other errors related to connectivity, google your symptoms and application server combination.

SQL exceptions

Consult your database documentation as SQL has some database specific differences (sad). It is best to validate your SQL outside of Confluence before putting it on a page. Use a database admininstrator tools (pgAdmin for instance), some general SQL client, or various Eclipse database plugins.