Hi Ole,
Ole Husgaard wrote:
OH> Currently we have one global timeout value that may be
OH> set programmatically with TM.setTransactionTimeout().
OH> We have no way of setting the default of this in the
OH> configuration files, and I see no reason why we shouldn't
OH> have that. But I am not yet familar with JMX, so I would
OH> rather if someone else could implement that.
Done: the default transaction timeout can be configured via
jboss.jcml:
<mbean name="DefaultDomain:service=TransactionManager">
<attribute name="TransactionTimeout">60</attribute>
</mbean>
The timeout is set in seconds.
BTW, when I tested this, I've noticed that if the timeout is too
small, jBoss behaves incorrectly: the error message
Transaction XidImpl:on/0 timed out
appears in server log, but client doesn't receive any exception.
OH> For seperate per-bean default timeout values things get
OH> a bit more complicated, but still possible (at least in
OH> theory). Problem is, the JTA TM.begin() method gives us
OH> little information about the caller.
I hope the solution will be found.
Best regards,
Oleg
