Release Notes - Red Hat Issue Tracker

Release Notes - JBoss Transaction Manager - Version 4.16.1 - HTML format

Configure Release Notes

Feature Request

[JBTM-1028] - Allow the ant build to publish artifacts to the local .m2 folder without having to upload to nexus

Bug

[JBTM-990] - com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction catches and throws a NullPointerException instead of checking if it is null first
[JBTM-1011] - Orphaned Subordinates are not being culled during XTS recovery
[JBTM-1012] - fix exception use in FileSystemStore.closeAndUnlock
[JBTM-1023] - JTA when putResource is called on a transaction that has been committed, the call is allowed to proceed. This is against the spec.

Task

[JBTM-817] - Automate execution of XTS crash recovery tests

Enhancement

[JBTM-1025] - Ensure object store is empty before each XTS crash-recovery test
[JBTM-1027] - Create a script to simplify XTS crash-recovery logs

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.

Release Notes - JBoss Transaction Manager - Version 4.16.1
                                                
<h2>        Feature Request
</h2>
<ul>
<li>[<a href='https://issues.redhat.com/browse/JBTM-1028'>JBTM-1028</a>] -         Allow the ant build to publish artifacts to the local .m2 folder without having to upload to nexus
</li>
</ul>
            
<h2>        Bug
</h2>
<ul>
<li>[<a href='https://issues.redhat.com/browse/JBTM-990'>JBTM-990</a>] -         com.arjuna.ats.internal.jta.transaction.jts.BaseTransaction catches and throws a NullPointerException instead of checking if it is null first
</li>
<li>[<a href='https://issues.redhat.com/browse/JBTM-1011'>JBTM-1011</a>] -         Orphaned Subordinates are not being culled during XTS recovery
</li>
<li>[<a href='https://issues.redhat.com/browse/JBTM-1012'>JBTM-1012</a>] -         fix exception use in FileSystemStore.closeAndUnlock
</li>
<li>[<a href='https://issues.redhat.com/browse/JBTM-1023'>JBTM-1023</a>] -         JTA when putResource is called on a transaction that has been committed, the call is allowed to proceed. This is against the spec.
</li>
</ul>
    
<h2>        Task
</h2>
<ul>
<li>[<a href='https://issues.redhat.com/browse/JBTM-817'>JBTM-817</a>] -         Automate execution of XTS crash recovery tests
</li>
</ul>
                                                                                                                                                                    
<h2>        Enhancement
</h2>
<ul>
<li>[<a href='https://issues.redhat.com/browse/JBTM-1025'>JBTM-1025</a>] -         Ensure object store is empty before each XTS crash-recovery test
</li>
<li>[<a href='https://issues.redhat.com/browse/JBTM-1027'>JBTM-1027</a>] -         Create a script to simplify XTS crash-recovery logs
</li>
</ul>