Re: [dbcp] java.io.EOFException, underlying cause: null

2009-04-20 Thread Matthew Hixson
bcUrl),null); new PoolableConnectionFactory(connectionFactory,pool,null,null,false,true); return(new PoolingDataSource(pool)); Thanks, -M@ On Apr 20, 2009, at 1:28 AM, Mark Thomas wrote: Matthew Hixson wrote: Occasionally I'll see this exception in our logs. I have setup the poo

[dbcp] java.io.EOFException, underlying cause: null

2009-04-19 Thread Matthew Hixson
Occasionally I'll see this exception in our logs. I have setup the pool like so: GenericObjectPool pool = new GenericObjectPool(null); pool.setWhenExhaustedAction(GenericObjectPool.WHEN_EXHAUSTED_GROW); pool.setTestOnBorrow(true); pool.setTestOnReturn(true); pool.setTestWhileIdle(true); Is th

[dbcp] scaling to 20 connection pools

2009-04-18 Thread Matthew Hixson
I am maintaining a webapp that has been using the Protomatter JDBC connection pool package for the past several years. Due to some changes in our requirements we need to find a connection pool provider that doesn't have a problem maintaining 20 or so pools for connections to different data