| ORDS connection pools [message #678223] |
Mon, 18 November 2019 11:33 |
John Watson
Messages: 8960
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
I usually deploy ORDS to Tomcat, with the jdbc connection pool configured in defaults.xml (just an example) like this:
<entry key="jdbc.InitialLimit">15</entry>
<entry key="jdbc.MaxLimit">50</entry>
<entry key="jdbc.MinLimit">15</entry>
The behaviour over all releases I've worked with is that you start up Tomcat and it doesn't touch the database. Then you hit it with an ords URL, and the connection pools get established. Time goes by, and the connections get dropped and re-created.
What I want to do is force ORDS/Tomcat to establish the pools as soon as Tomcat is started, without waiting for a request. And then be able to control the frequency with which idle connections are dropped and re-made. I cannot find the settings to do this. Can anyone advise?
Thank you for any insight.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
