I am using DBCP 1.1 stable.
I shall give details later but a quick question. In
PoolablePreparedStatement.close() method it is checking isClosed() and
throws SQLException if it is already closed. What is its intention ?.
Antony Paul
----- Original Message -----
From: "Dirk Verbeeck" <[EMAIL PROTECTED]>
To: "Jakarta Commons Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, April 21, 2004 1:45 AM
Subject: Re: [DBCP] PreparedStatements throwing Already closed Exception.
> What version are you using? (v1.1 or nightly build)
> Can you give a small code example of the problem?
>
> -- Dirk
>
> Antony Paul wrote:
>
> > Hi all,
> > I was using DBCP quite well without any problem. Yesterday I had an
idea
> > to reap the benefit of PreparedStatement pools because 95% of our
> > application uses PreparedStatements. But to my surprise it is throwing
> > SQLException("Already closed") in PoolablePreparedStatement when
> > PreparedStatement pooling is turned on. What is the need of throwing an
> > exception here against the default behaviour of ordinary
PreparedStatements
> > ?. I think this is unwanted as it forces to set a PreparedStatement to
null
> > on closing and in the finally block again check it for null when the
same
> > prepared statement is used. Or is there anything as not use same
> > PreparedStatement for another sql statement ?. If so please document it
in
> > the configuration section and API of DBCP.
> >
> > Antony Paul
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
