"mark.little(a)jboss.com" wrote : Yes, but in TP systems you never take a chance,
no matter how small. Plus, I'm sure someone made a similar comment about date fields
back in the 1960's and looks what happened come the year 2000! ;-)
Now your argument sounds a bit like a rhetorical one, as the year 2000 issue was an
entirely different problem! ;-)
Unless you use unbounded transaction ids you will be always taking a chance, which of
course should be very, very, very small. Since the XA spec places an upper limit on the
size of Xids, there is no way around this in the XA design space. It is really a matter of
reaching a point that is safe enough.
Half a million years at one million TPS is certainly safe enough. Note that this would not
be an upper limit on the entire lifetime of the TP system, but just on the time a
transaction may remain in the active state or in a heuristically completed (and not yet
forgotten) state. In other words, it is just an upper limit on the time any given
transaction may exist in the current set of transaction log files. Half a million years is
actually way over the top for that; a few months would probably be enough.
I understand "long transactions" are becoming increasingly important, but... Do
you really expect them to be that long? ;-)
Regards,
Francisco
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977073#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...