Mantis - Resin
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4664 minor always 07-08-11 15:05 10-07-11 11:55
Reporter: rickHigh Platform:  
Assigned To: ferg OS:  
Priority: normal OS Version:  
Status: closed Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 4.0.24  
Summary: 0004664: Add minium database connection pool size to handle bursts for bursty applications
Description: Notes sent to customer:

Regarding your question around Oracle pooling and connections and your comments about how long it takes to create an Oracle connection and the burst nature of your application, we decided to add a minimum pool size feature. Current our DB pool has a max connection pool size, but not a minimum connection pool size. This will be in release 4.0.20 or 4.0.21.


Currently, we create a connection if it does not exist when you call dataSource.getConnection(), and again you seemed concerned that this is an expensive operation and it might be happening too often.

Workaround

Until we add the minimum pool feature, note that the connection stays around until it times out based on max-idle-time. If you feel that the system is creating connection too often to Oracle and you want to reuse connections from burst to burst, just set the max-idle-time to a much higher value (24 hours) as it defaults to 30 seconds (you also want to bump up max-pool-time and max-active-time to be several factors of max-idle-time, i.e., 48 hours and 72 hours).

Since the connection is going to be around a lot longer, you may want to setup a ping on it so you can verify it stays alive.

http://caucho.com/resin-4.0/admin/database.xtp#driverconfig [^]
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:

Notes
(0005551)
ferg   
10-07-11 11:55   
env/11b4