commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dain Sundstrom (JIRA)" <>
Subject [jira] Updated: (DBCP-207) DBCP 1.2.1 incompatible with Informix (driver doesn't support setReadOnly(...))
Date Fri, 20 Jul 2007 00:36:06 GMT


Dain Sundstrom updated DBCP-207:

    Attachment: DBCP-207.patch

Already fixed for PoolingDataSource, but PerUserDataSource and SharedPoolDataSource still
always set this value.  These data sources use a primitives for the read only,  transaction
isolation and auto commit default values so there is not way to see if the value was not set.
 This patch checks if the read-only and auto-commit values are already set before changing
them which should setReadOnly from being called. 

> DBCP 1.2.1 incompatible with Informix (driver doesn't support setReadOnly(...))
> -------------------------------------------------------------------------------
>                 Key: DBCP-207
>                 URL:
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>         Environment: using the pooling driver component with an informix driver
>            Reporter: Kimberly Baer
>             Fix For: 1.3
>         Attachments: DBCP-207.patch
> I recieved an error using commons-dbcp-1.2.1.jar and ifxjdbc.jar for my informix driver:

> org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool exhausted 
> at org.apache.commons.dbcp.PoolingDriver.connect( 
> at java.sql.DriverManager.getConnection( 
> at java.sql.DriverManager.getConnection( 
> at ConnectionPoolingTest.main( 
> Caused by: java.util.NoSuchElementException: Could not create a validated object, cause:
Read only mode not supported 
> at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(

> at org.apache.commons.dbcp.PoolingDriver.connect( 
> I will look into the comment provided by Dirk in bug ID DBCP-127 (version 1.1), but it
appears this bug still has an impact in the 1.2.1 version. If anyone has any other suggestions,
they would be greatly appreciated. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message