Confluence 3.4 has reached end of life
Check out the [latest version] of the documentation
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 3. Edit 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.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/.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>
You will need to reapply these changes when upgrading Confluence, as the original
databaseSubsystemContext.xml file changes from version to version.
