Confluence Docs 3.0 : Configuring database query timeout This page last changed on Oct 20, 2008 by mryall. If database queries are taking too long to perform, and your application is becoming unresponsive, you can configure a timeout for database queries. There is no default timeout in Confluence. To configure a database query timeout, do the following on your test server: 1. Shut down Confluence. 2. Extract `databaseSubsystemContext.xml` from the `confluence-x.x.x.jar` that is in `confluence/WEB-INF/lib/`, and put a copy in `confluence/WEB-INF/classes/`. 3. Edit `confluence/WEB-INF/classes/databaseSubsystemContext.xml` to add the defaultTimeout property to the "transactionManager" bean:
    <bean id="transactionManager" class="org.springframework.orm.hibernate.HibernateTransactionManager">
        <property name="sessionFactory">
            <ref bean="sessionFactory"/>
        </property>
        <property name="defaultTimeout" value="120"/>
    </bean>
The timeout is measured in seconds and will forcibly abort queries that take longer than this. In some cases, these errors are not handled gracefully by Confluence and will result in the user seeing the Confluence error page. 4. Start Confluence. Once the timeout is working properly in your test environment, migration the configuration change to Confluence. You will need to reapply these changes when upgrading Confluence, as the original `databaseSubsystemContext.xml` file changes from version to version.

Document generated by Confluence on Nov 05, 2009 23:34