Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

JDBC connections timing out

247917Jul 15 2008 — edited Jul 16 2008
I am working on improving performance of an EJB3 application deployed on Oracle AS 10.1.3. One of the suggestion Oracle makes for improving performance is reusing JDBC connections. Under http://download-uk.oracle.com/docs/cd/B31017_01//core.1013/b28942/top_issues.htm#BCFEBHAC Oracle recommends setting min-connections parameter to a value greater than the default of 0. This will force the server to always maintain connections in the pool.

I tried that technique and it failed miserably. In the environment where the Oracle AS is deployed, all the idle connections are forced to time out after 15 minutes (enforced by CyberSecurity). If the JDBC connection pool used by my application is configured to have a positive number of connections, the application stops functioning after the 15 minutes of idle time. Refreshing a the connection pool solves the problem, until the next time out happens.

As a result I am unable to set the min-connections to anything but 0.

Is this supposed to happen with the connections maintained by the application server? Is there a way to prevent the connections from timing out? Is there a way to force the server to detect that the connections timed out and create new connection.

Thank you,

Michael
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 13 2008
Added on Jul 15 2008
1 comment
783 views