[ https://jira.jboss.org/browse/JBTM-108?page=com.atlassian.jira.plugin.sys... ] Andrew Dinn closed JBTM-108. ---------------------------- Resolution: Rejected This doesn't really make sense given the current reaper design which uses the old DYNAMIC mode to decide when to wake up. It only made sense when the wake-up mode was FIXED allowing a lot of cancelled transactions to build up and hten ladnign the reaper with a large burst of work to perform. This situation should not arise often with the latest design (it does not appear to) and even if it does it indicates an app problem -- lots of timed out TXs means the app's TX timeout is misconfigured or the app is overloaded. So, I'm rejecting this because I don't see it as being particularly helpful now and I don't see the point of complicating the behaviour of the reaper merely to help out misconfigured apps. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira