Product SiteDocumentation Site

JBoss Transaction manager 4.16

Release Notes

Release Notes for JBoss Transaction Manager

Misty Stanley-Jones

JBoss.org

Legal Notice

Copyright © 2011 JBoss.org.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
All other trademarks are the property of their respective owners.
Abstract
Release notes for ArjunaCore, ArjunaJTA, ArjunaJTS, and XTS components of the JBoss Transaction Manager.

1. ArjunaCore
2. ArjunaJTA
3. ArjunaJTS
4. XTS
5. Recovery
6. JCA
A. Revision History

1. ArjunaCore

New features
JBTM-573 ArjunaCore now includes a command-line tool for manually pruning log files.
TBD
JBTM-796 All ObjectStore types supported by the ObjectStoreAPI are now supported by MBean ObjStoreBrowserMBean.
Originally, ObjStoreBrowserMBean was only known to support file-based ObjectStores. It now implements the ObjectStoreAPI, and works with all types of ObjectStores supported by the API.
Resolved issues
JBTM-575 RollbackException now behaves as it did in JBoss Application Server 4.3 and earlier, providing debugging information about the cause of the exception.
In JBoss Application Server 4.2 and previous, when a transaction rolled back, the RollbackException included the root cause of the exception. In JBoss Application Server 5.1, the exception no longer included this information, even though the information can still be found in a different area of the log file. Code which relied on the root cause information included in the exception no longer worked as expected.
The debugging information has been put back into the exception, so that it works as it did previously. The following algorithm is used:
  1. If setRollbackOnly() is called before commit(), the initCause is setRollbackOnly called from..., regardless of anything that may go wrong during the commit. beforeCompletions are not called.
  2. If getDeferredThrowable is not null, the initCause is the deferredThrowable, even if setRollbackOnly is also called before the exception is received.
  3. If setRollbackOnly was called, it is the root cause. This covers the case where a beforeCompletion calls setRollbackOnly but does not throw an exception.
This fix allows you to code against the root cause of the RollbackException.
JBTM-814 TSR implementations now implement ObjectFactory.
TSR implementations have been modified to implement ObjectFactory.
JBTM-811 The finalizer has been removed from the StateManager.
The StateManager no longer includes the finalizer.
JBTM-599 A synchronization in CacheStore has been fixed.
Removing threads operating on AsyncStore did not check to see if the cache was full, and did not notify AsyncCache to wake up. This could cause a stalling condition, if there were more removes than adds to the cache. Removes now check to see if the cache is full, and notify AsyncCache accordingly.