[
https://issues.apache.org/jira/browse/DBCP-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
peeyush joshi updated DBCP-397:
-------------------------------
Description:
Previously our application was using following setting with DBCP 1.2.1
<property name="poolPreparedStatements">
<value>true</value>
<property name="maxOpenPreparedStatements">
<value>40</value>
And in the oracle DB around 30 open cursors were found during high load.
But when we upgrade DBCP version to 1.3 even during normal load conditions the
number of open cursors keeps on increasing and reaches up to the maximum
allowed limit (i.e. 1000 cursors per connection). It results an exception
"nested exception is java.sql.SQLException: ORA-01000: maximum open cursors
exceeded". After this exception no DB query is processed.
Same problematic behavior is noticed with DBCP 1.4.
When poolPreparedStatements is set to false the number of maximum open cursors
never goes beyond 6 (in all DBCP versions 1.2.1/1.3/1.4)
was:
Previously our application was using following setting with DBCP 1.2.1
<property name="poolPreparedStatements">
<value>true</value>
<property name="maxOpenPreparedStatements">
<value>40</value>
And in the oracle DB around 30 open cursors were found during high load.
But when we upgrade DBCP version to 1.3 even during normal load conditions the
number of open cursors keeps on increasing and reaches up to the maximum
allowed limit (i.e. 1000 cursors per connection). It results an exception
"nested exception is java.sql.SQLException: ORA-01000: maximum open cursors
exceeded".
Same problematic behavior is noticed with DBCP 1.4.
When poolPreparedStatements is set to false the number of maximum open cursors
never goes beyond 6 (in all DBCP versions 1.2.1/1.3/1.4)
> Exception ORA-01000 [Number of open cursors exceeds the limit] is faced when
> prepared statement pooling is enabled in DBCP 1.3
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: DBCP-397
> URL: https://issues.apache.org/jira/browse/DBCP-397
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.3, 1.4
> Environment: jdk 1.6_u25
> dbcp 1.3/1.4
> SunOS
> Spring 2.0.6
> Oracle 10.0.2
> Reporter: peeyush joshi
>
> Previously our application was using following setting with DBCP 1.2.1
> <property name="poolPreparedStatements">
> <value>true</value>
> <property name="maxOpenPreparedStatements">
> <value>40</value>
> And in the oracle DB around 30 open cursors were found during high load.
> But when we upgrade DBCP version to 1.3 even during normal load conditions
> the number of open cursors keeps on increasing and reaches up to the maximum
> allowed limit (i.e. 1000 cursors per connection). It results an exception
> "nested exception is java.sql.SQLException: ORA-01000: maximum open cursors
> exceeded". After this exception no DB query is processed.
> Same problematic behavior is noticed with DBCP 1.4.
> When poolPreparedStatements is set to false the number of maximum open
> cursors never goes beyond 6 (in all DBCP versions 1.2.1/1.3/1.4)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
