|Yes and no. The default should force users that do not know what they
|are doing to use relatively short transactions.
|Users that are aware of the problems with long transactions should be
|able to change the default timeout.
|
|Some transaction MBean setting would probably be the right thing.
Yes but
1- The time stuff is still a bit buggy. When one is timeout, it seems to
throw the container off (locking is not cleaned? as of this morning)
2- it strikes me as an application dependent entity. So the MBean we are
talking about is app dependent or takes an app identifier to set the stuff
on the right container. The tx being handed out by the global pool need to
have the setTransaction time out at the container level and I don't believe
we have indirection right now.
In fact the last point is really 2 point
a- we need an app specific MBean (or equivalent access) not written yet but
an IMPORTANT step in my mind
b- we need container indirection on setting the txTimeOut from the generic
pool, not done (afaik ?)
marc
|
|Best Regards,
|
|Ole Husgaard.
|
|
