[ https://issues.jboss.org/browse/JBTM-2256?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2256: ------------------------------------- Implementing the fix will prevent us creating a byteman race condition test case for the issue as it will (assuming the correct recovery modules are configured) no longer be possible for the expiry scanner to start before the Implementationsx.java is loaded. A comment in the code that explains the issue (i.e. ExpiredEntryMonitor.startUp(); _MUST_ be called after _periodicRecovery = new PeriodicRecovery(threaded, useListener); and provide more details on that) is the best thing to ensure its not reverted, plus Gytis should also cherry-pick the test I have written https://github.com/tomjenkinson/narayana/compare/4.17...JBTM-2256 during verification of the issue. Even though Byteman verification isn't possible, the test could still alert us if something were to change in this area in the future. On the link I provided above you will see that I have added byteman to verify the failure without the fix. Once the fix is applied the test will hand as the race condition no longer exists so that specific commit should not be cherry-picked but the underlying test can be. -- This message was sent by Atlassian JIRA (v6.3.1#6329)