Subject Re: FBWrappingDataSource Blocking Timeout
Author llafranc78
Hi Rick :)

I'm not so experienced with DataSource and ManagedConnections, but
maybe your problem is the idleTimeout, not the blockingTimeout. The
IdleRemover sees that your FBWrappingDataSource had no activity for a
period > idleTimeout and tries to put it back in the pool, but the
last transaction wasn't committed and so it throws the Exception.

Try setting idleTimeout to a greater value, or find where you don't
commit the transaction.


--- In Firebird-Java@y..., "Rick Fincher" <rnf@t...> wrote:
> Hi All,
> What is the blocking timeout in FBWrappingDataSource?
> I'm using Firebird and the level 4 JDBC driver with Tomcat and it
works initially, but fails after a period of time with errors like
"java.lang.IllegalStateException: Can't destroy managed connection
with active transaction" and null exceptions when making requests for
a connection to the database.
> I suspect that it has something to do with timeout settings or the
maximum number of connections.
> Also, Tomcat uses the database for user authentication with FBDriver
and my web apps use FBWrappingDataSource for the pooling capability.
Could there be some problem with using those simultaneously?
> The full error message is below.
> Thanks,
> Rick
> java.lang.IllegalStateException: Can't destroy managed connection
with active
> transaction
> at
> at
> 53)
> at
> ava:181)
> at org.firebirdsql.jca.IdleRemover$
> at
> getting new fbwds connection failed! Error: java.sql.SQLException:
> getting connection: javax.resource.ResourceExcep
> tion: No ManagedConnections Available!