Subject | Transaction Interleaving? |
---|---|
Author | rickcarragher |
Post date | 2006-02-27T16:44:11Z |
Hi, I'm using the Firebird 1.5.0 JCA driver, and I've recently updated
to 1.5.6. Deploying to JBoss 3.2.7.
We're seeing "failure to delist resource" on open connections in the
JBoss connection pool. This typically happens when the system is very
loaded, or after it has been up for a while. When the connection pool
size is set to 50, it seems to go away, but there's no way our app
needs 50 connections.
After some research, I'm wondering if this is an XA Transaction
Interleaving problem. Is this possible? Does the JCA adapter support
this? Should I restrict Jboss to to <track-connection-by-tx/>?
Should I use the JDBC driver directly instead of the JCA adapter?
Thanks,
Rick
to 1.5.6. Deploying to JBoss 3.2.7.
We're seeing "failure to delist resource" on open connections in the
JBoss connection pool. This typically happens when the system is very
loaded, or after it has been up for a while. When the connection pool
size is set to 50, it seems to go away, but there's no way our app
needs 50 connections.
After some research, I'm wondering if this is an XA Transaction
Interleaving problem. Is this possible? Does the JCA adapter support
this? Should I restrict Jboss to to <track-connection-by-tx/>?
Should I use the JDBC driver directly instead of the JCA adapter?
Thanks,
Rick