track-connection-by-tx

[rcarragher]

I'm using JBoss 3.2.7 with an older Firebird JCA adapter (1.5.0 beta3) which I'm looking to upgrade immediately. The big problem with it is that after it runs for a while, I get "Failure to delist resource" exceptions when attempting to get a connection from the pool. It's an xa connection factory.

After much research, it looks like this is due to the JCA adapter's failure to support transaction interleaving, and that putting <track-connection-by-tx/> in the connection factory config will solve the problem.

My question is, if the new JCA adapter fixes the problem, should I leave the track-connection-by-tx setting on? What's more efficient/performant?

Rick

[adrian.brock]

"rcarragher" wrote:

My question is, if the new JCA adapter fixes the problem, should I leave the track-connection-by-tx setting on? What's more efficient/performant?

Not setting track-connection-by-tx is more efficient.
See XAResource interleaving in the JTA Spec.

[rcarragher]

I communicated with the author of the Firebird JCA adapter, and he indicated that <track-connection-by-tx/> is a required setting for Firebird. Does it make sense to update the FirebirdDS.xml example in the JBoss distribution?

[starksm64]

If its required, yes. Create a jira issue to track it.
http://jira.jboss.com/jira/browse/JBAS

[adrian.brock]

http://jira.jboss.com/jira/browse/JBAS-2888