[ 
https://issues.apache.org/jira/browse/DBCP-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dain Sundstrom resolved DBCP-207.
---------------------------------

    Resolution: Fixed

Committed a fix for this specific problem, and created a JIRA for converting 
all default values to non-primitive types.  This way only configured default 
values will be set.

Sending        
src/java/org/apache/commons/dbcp/datasources/PerUserPoolDataSource.java
Sending        
src/java/org/apache/commons/dbcp/datasources/SharedPoolDataSource.java
Transmitting file data ..
Committed revision 558850.


> DBCP 1.2.1 incompatible with Informix (driver doesn't support 
> setReadOnly(...))
> -------------------------------------------------------------------------------
>
>                 Key: DBCP-207
>                 URL: https://issues.apache.org/jira/browse/DBCP-207
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>         Environment: using the pooling driver component with an informix 
> driver
>            Reporter: Kimberly Baer
>            Assignee: Dain Sundstrom
>             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(PoolingDriver.java:183) 
> at java.sql.DriverManager.getConnection(DriverManager.java:539) 
> at java.sql.DriverManager.getConnection(DriverManager.java:211) 
> at ConnectionPoolingTest.main(ConnectionPoolingTest.java:105) 
> 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(GenericObjectPool.java:806)
>  
> at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:175) 
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to