Subject RE: [IB-Java] Re: Built in pooling added to jca-jdbc driver
Author Paulo Gaspar

Hum... I promised taking care of the logging bit but I am still
missing the time to do it.

Your error suggests that you are missing a Connection.commit() or
Connection.rollback() call to finalize some transaction. Check
your code.


In my own DB Connection pool I include rolling back connections
with pending transactions in the returned-to-the-pool connection
cleanup process. Questions:
- Can it be that this is missing in the current implementation?
- What makes more sense: the silent automatic rollback() I
describe or a noisy one that raises an exception?

Have fun,
Paulo Gaspar

> -----Original Message-----
> From: jwcanada [mailto:jwcanada@...]
> Sent: Monday, January 07, 2002 2:38 PM
> To:
> Subject: [IB-Java] Re: Built in pooling added to jca-jdbc driver
> David,
> It seems that the pooling is working, except
> 1) ds.getConnection() without username, password
> 2) I tried it in a project, there are few log exception messages as
> follows:
> java.lang.IllegalStateException: Can't destroy managed connection
> with active t ransaction
> at org.firebirdsql.jca.FBManagedConnection.destroy
> (FBManagedConnection.j ava:323)
> at org.firebirdsql.jca.ManagedConnectionPool.doDestroy
> (ManagedConnection
> at org.firebirdsql.jca.ManagedConnectionPool.removeTimedOut
> (
> at org.firebirdsql.jca.IdleRemover$
> at
> 3) Are there any easy way to disable logging?
> Thank you for the nice work.
> jw
> To unsubscribe from this group, send an email to:
> Your use of Yahoo! Groups is subject to