Hi,
Jason Dillon wrote:
> What are the TX timeout semantics for the JBoss tx manager? Once a given tx
> starts does it have a finite time to finish before it times out, or is it's
> lifetime more dynamic?
A constant (configuration setting) time from tx start to timeout.
> For example, if I have Bean1 that invokes Bean2 which then invokes Bean3.
> If the timeout is 5 minutes, does the entire call chain have 5 minutes to
> finish or does each bean method invoke have 5 minutes?
>
> Assuming it is the first, are there any plans to make this more dynamic in
> the future?
Not currently. We should also be careful, as the JBoss
core is using JTA _only_, in order to avoid dependencies
on any particular TM implementation. The JTA API cannot
directly support a more dynamic timeout.
In any case there _has_ to be a fixed upper limit on the
time that a tx may live, or buggy bean code could keep
the transaction alive forever, thus keeping locks on
resources forever.
But the idea of having some shorter timeout on single
invocations with an inherited tx ctx is nice.
Maybe it would be possible the hack the proxy code used
for outgoing calls from the server to add an extra-TM
timer that would mark the tx for rollback only, if the
invocation does not return soon enough?
Best Regards,
Ole Husgaard.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development