.png?version=1&modificationDate=1662627367996&cacheVersion=1&api=v2&width=226&height=72)
Data source configuration differences starting with Confluence 5.8 - 8.x
- Randall Ward
- Smita Nair
- Sireesha Dugginapeddi [Appfire] (Inactive) (Deactivated)
There was a significant change in configuration values between Tomcat 7 (before Confluence 5.8) and Tomcat 8 (after Confluence 5.8). Confluence administrators must review their server.xml configuration and make adjustments.
| Max Connections | Default Max Connections | Wait Time for Connection from Pool | Default Wait Time for Connection from Pool | Example Settings | |
|---|---|---|---|---|---|
| Tomcat 8 | maxTotal | 8 | maxWaitMillis (in milliseconds) | -1 (no limit) |
|
| Tomcat 7 | maxActive | -1 (no limit) | maxWait (in seconds) | 30 (seconds) |
|
Why is this important?
Some customers have reported slow pages and related problems after upgrading Confluence. This is a likely consequence of running out of connections and having to wait for a connection to become available. The new default of 8 is very low for many higher volume use cases. This is exacerbated by a no limit wait which provides no feedback to page viewer that there is contention. By reviewing your previous configuration and updating it to use the new parameters, it should restore previous behavior.
Additional links
Log a request with our support team.
Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.