I have fixed your issue: http://issues.apache.org/bugzilla/show_bug.cgi?id=27320
The call to the setReadOnly is now optional. If you don't call setDefaultReadOnly on the PoolableConnectionFactory then the setReadOnly method will not be called on the connection.
Normally this should fix your problem with the Informix driver. Please test the next nightly build again.
-- Dirk
[EMAIL PROTECTED] wrote:
Hi Dirk,
Thanks for getting back to me... I have just downloaded the latest nightly builds for DBCP and pool and have recompiled and rerun the ManualPoolingDataSourceExample.java. I still get the exception...but it now looks like this....
Creating connection.
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool exhausted
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:148)
at ManualPoolingDataSourceExample.main(ManualPoolingDataSourceExample.java:169)
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:851)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:140)
... 1 more
Looks like you may be right and the Informix driver does not support the setReadOnly method. Anyway around this.... I'm fairly new to working with Databases and Java, so any help would be much appreciated.
Thanks again for the swift response,
Andrew Peirson.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
