Hi,

> Here's email from David Jencks:
>
> "I think this will be OK. Let's apply it and see if anything

breaks: I

> can't think of anything at the moment. I'd like to know what his

jboss

> settings are, in particular if he is using cache-by-transaction

(if I

> remember the parameter correctly). I don't understand at the

moment

> why cleanup would be called with an active transaction, unless

there is

> a large bug in jboss... but I haven't looked at the jboss code for

a

> long time."
>

cache-by-transaction? I don't remember jboss having this parameter
name in it's JCA configs. I know something called 'track-connection-
by-tx' which according to jboss documentation:

"Specifying a true value for this element makes the connection
manager keep an xid to connection map and only put the connection
back in the pool when the transaction completes and all the
connection handles are closed or disassociated (by the method calls
returning). As a side effect, we never suspend and resume the xid on
the connection's XAResource. This is the same connection tracking
behavior used for local transactions."

Currently my 'track-connection-by-tx' for my Firebird-JCA is unset.
But, after observing the FBManagedConnectionFactory Javadoc

" FBManagedConnectionFactory implements the jca
ManagedConnectionFactory interface and also many of the internal
functions of ManagedConnection. This nonstandard behavior is
required due to firebird requiring all work done in a transaction
to be done over one connection."

So, should i or should i not set 'track-connection-by-tx' to true?
Which one is safer ?

Thanks for any comment and answers.