My pipeline does a lot of database queries; everything works fine and the speed of processing even doubles, but when I process several requests in threads (10), the pool becomes exhausted; apparently the maximum number of active elements is 8;
Can the pool be configured somewhere, f.i. to support 20 active connections ?
regards,
Jan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I have setup a resource which uses pooled connections as follows:
type=pooled
dbUser=app_admfrm_d
dbPassword=xxx
dbDriver=oracle.jdbc.driver.OracleDriver
dbUrl=jdbc:oracle:thin:@devora.cc.cec.eu.int:1522:appgrhd
My pipeline does a lot of database queries; everything works fine and the speed of processing even doubles, but when I process several requests in threads (10), the pool becomes exhausted; apparently the maximum number of active elements is 8;
Can the pool be configured somewhere, f.i. to support 20 active connections ?
regards,
Jan
The max of 8 is a DBCP default. You would have to work out how to change that. Otherwise....
We rely on straight app server connection pools:
ie.
type=jndi
datasourceName=java:HSM_DS
They work fine.
Sherman
Sherman,
OK, the default is 8, so I changed the source by adding a parameter dbPoolSize which is configurable (in SimpleJdbc.java)
Jan