<friday-night-can't-sleep>
So when a timeout is trigered what happens to the bean instances... we need
to release them for sure, not only in cache but in the locking as well. I
am not sure this is properly done.
Also does the spec say anything about a time out on the tx and what the
clients should see? I mean if the clients must be notified we are in doo-doo
since we need a callback (can't really do that...) but if not then we need
to keep the state somewhere (the fact that it was rolledback) and it defeats
the purpose of the timeout which is to clear the resources.
Also do we know that it behaves well when we put in passivating caches? i.e.
does the timeout logic do anything to the instances? if not what is the
point?
</friday-night-paranoia>
pffff...... txs can't run for ever but we must be sure it is kosher with the
rest of the container... pfffffff
I don't think there is anything in the spec is there?
marc
_________________________
"Yes I am losing control"
_________________________
