The transaction manager will pass on any transaction level timeout information to the
resource manager, but it's up to the RM to decide what, if anything, to do with that
information.
Since the TM will drive a transaction timeout itself anyhow, the RM does not really need
to do anything proactive with the information. It's only worthwhile if you don't
trust the TM to come along and rollback the branch in a timely manner. That can happen if
the TM and RM are running as separate processes and the TM crashes, but it's not
common.
The utility really depends on your locking model and other resource (in the sense of
RAM/disk etc) usage constraints. If releasing resources promptly is important to you then
by all means put in your own rollback processing. Otherwise just implement getter/setter
for API compliance and do nothing with the information.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186364#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...