Re: DBCP validation query: how to use?

2002-06-09 Thread Juozas Baliuka

Hi,
 I think you need to enable ping in configuration.
But you can solve this in postgres :
1. use BYTEA type for bynary strings.
2. check the last driver version, I am not sure it is fixed in the last
versoin, but it
is no problems to fix it, driver is open source. Current STABLE version
has this bug.
Escape table you can find in user's guide.


 I'm using the latest DBCP release to create a Datasource as follows,
 against a PostgreSQL database:

 Class.forName(org.postgresql.Driver);
 ObjectPool connectionPool = new GenericObjectPool(null);
 ConnectionFactory connectionFactory = new
 DriverManagerConnectionFactory(jdbc:postgresql://localhost/mydb,
 bryan, nopw);
 String validationQuery = select 1 as test;
 PoolableConnectionFactory poolableConnectionFactory = new
 PoolableConnectionFactory(connectionFactory, connectionPool, null,
 validationQuery, false, true);
 dataSource = new PoolingDataSource(connectionPool);

 I'm chasing down a different bug which is hosing my postgres connections
 - trying to insert strings into TEXT fields, which contain nulls.
 Evidently Postgres doesn't like that, and hoses the connection.

 But, according to how I've initialized the pool (above), should DBCP be
 testing my connections with my validation query, noticing my hosed
 connections, and creating new ones for me? Observed behavior indicates
 otherwise... It keeps resuing the hosed connection to future calls of
 dataSource.getConnection(), throwing off future executing code.

 Am I doing something wrong?

 Thank you,
 Bryan





--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: DBCP validation query: how to use?

2002-06-09 Thread Bryan Field-Elliot

Thanks,

Actually the problem is in my code, there should not be any nulls at all
in the String I'm trying to insert. It's supposed to be a normal
human-readable string.

But talking about DBCP again -- how do I enable ping in configuration
of DBCP?

I'm looking at the source code for DBCP, and the validateObject method
in PoolableConnectionFactory is where the test occurs (on your
validation query). But either the code doesn't work, or validateObject
is never called in the first place. 

Again, help would be appreciated!

Bryan

On Sun, 2002-06-09 at 01:34, Juozas Baliuka wrote:

Hi,
 I think you need to enable ping in configuration.
But you can solve this in postgres :
1. use BYTEA type for bynary strings.
2. check the last driver version, I am not sure it is fixed in the last
versoin, but it
is no problems to fix it, driver is open source. Current STABLE version
has this bug.
Escape table you can find in user's guide.





Re: DBCP validation query: how to use?

2002-06-09 Thread Juozas Baliuka


It is code in GenericObjectPool. _testOnBorrow  must be set to true.
Sorry, but I dont know how to set it in DBCP, I believe somebody more
competent will respond to your message.
..
if( _testOnBorrow  !_factory.validateObject(pair.value)) {
try {
_factory.passivateObject(pair.value);
} catch(Exception e) {
; // ignored, we're throwing it out anyway
}
_factory.destroyObject(pair.value);
} else {
.

 Thanks,

 Actually the problem is in my code, there should not be any nulls at all
 in the String I'm trying to insert. It's supposed to be a normal
 human-readable string.

 But talking about DBCP again -- how do I enable ping in configuration
 of DBCP?

 I'm looking at the source code for DBCP, and the validateObject method
 in PoolableConnectionFactory is where the test occurs (on your
 validation query). But either the code doesn't work, or validateObject
 is never called in the first place.

 Again, help would be appreciated!

 Bryan

 On Sun, 2002-06-09 at 01:34, Juozas Baliuka wrote:

 Hi,
  I think you need to enable ping in configuration.
 But you can solve this in postgres :
 1. use BYTEA type for bynary strings.
 2. check the last driver version, I am not sure it is fixed in the
last
 versoin, but it
 is no problems to fix it, driver is open source. Current STABLE
version
 has this bug.
 Escape table you can find in user's guide.





--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]