Hey
> |No, I really mean one tx in one container. If not, then there will
> |be severe
> |performance penalties on finders. And I mean *truly bad*.
> |
> |Why is not one container per tx realistic?
>
> well simple scenario:
> Bean and servlet do app front end, connector does access to DB or RS/6000
> install somewhere with DB2 and the applications is distributed, you have
> distributed Tx. Assuming one Tx in ONE container is a tough one imho.
Your scenario says nothing about multiple container per tx. Try again.
The only reason I can see for getting multiple containers per tx is if there
is some resource that is only available in some cluster node, and the tx was
started in another node. Other than that we should be fine I think. Again,
if we can keep a tx within a node we're pretty ok, otherwise finders will be
total killers.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
