Issue Details (XML | Word | Printable)

Key: JAHIA-158
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Olivier Vit
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Jahia Web Content Management Server (WCMS)

dbpool.properties isn't updated by the configuration wizard- can lead to server freeze

Created: 16/Sep/04 10:32   Updated: 20/Sep/05 17:36   Resolved: 07/Oct/04 14:27
Return to search
Component/s: Installation and Environment (J2EE, Apache,...)
Affects Version/s: WCM 4.0.4
Fix Version/s: WCM 4.0.5

Time Tracking:
Not Specified


 Description  « Hide
Jahia is now using Apache org.apache.commons.dbcp for the connection pool

But after the installation process, all entries in dbpool.properties are
commented out and then the connection pool is running with default values (see
http://jakarta.apache.org/commons/dbcp/configuration.html)

=> max number of connections is 8 :
under load the server will sload down dramatically
=> maxWait is infinite :
when connections are not properly released, they keep on being busy and the
server will freeze completely, waiting to be able to create a new connection (it
will never happen if the default 8 are already opened)

We are running fine with maxWait=5000 (5s) against postgresql 7.4.3

Serge Huber added a comment - 07/Oct/04 14:27
New default values in dbpool.properties
int.maxActive=100
int.maxIdle=10
long.maxWait=10000

This should provide for better default values, but might fail on database setups that do not support 100 connections.