JBTM-2229 Prevent an issue when recovering CMR where they activate an AA that does not have Serializable XAR which leads to the Xid being removed from XARM which when the AARM then tries to recover the AA means a corresponding XAR cannot be located for the Xid and an error message is reported
Updated to 4.17.22.Final
Updated to 4.17.23.Final-SNAPSHOT
[JBTM-2238] Expose CMR records as MBeans
[JBTM-2241] Always satisfy revcovery helper removal requests
[JBTM-2242] Do not delay deployments during recovery passes
[JBTM-2242] Wait for threads before testing assertions
JBTM-1341. Do not allow invalid node ids
JBTM-2255. Do not return StatusCommiting, if transaction was commited by the original transaction manager
Revert "JBTM-2255. Do not return StatusCommiting, if transaction was commited by the original transaction manager"

This reverts commit 706a9d4c99392db4404bd8c2f55d947b2862c6fd.
JBTM-2256. Remove race condition between recovery manager initialization and expiry scanner
JBTM-2256 reproducer to ensure that the scanner is called after periodic recovery loads the modules
JBTM-2216 Updated to check to make sure that there were some Xids recovered in the first scan, if the first scan failed it is possible that there are no Xids to check
JBTM-2263 Move the web-app schema down to 2.5 to prevent schema validation issues
JBTM-2255. Do not change status from committed to committing in replay_completion
Updated to 4.17.23.Final
Updated to 4.17.24.Final-SNAPSHOT