[ https://issues.jboss.org/browse/ISPN-2177?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2177: -------------------------------- Description: There are several collections holding transaction related information in the AbstractCacheTransaction: - lockedKeys: this holds all the keys that were actually locked on the local node - affectedKeys: this holds all the keys that were acquired by the transaction allover the cluster - backupKeyLocks: this holds all the locks for which the local node is a secondary data owner. To do: - affectedKeys belongs to LocalCacheTransaction(subclass) and no point in having it in the AbstractCacheTransaction - a better name for affectedKeys might be "clusterLockedKey" and for lockedKeys --> localLokedKeys - also add a Javadoc explaining the correlation between these key groups was: There are several collections holding transaction related information in the AbstractCacheTraansaction: - lockedKeys: this holds all the keys that were actually locked on the local node - affectedKeys: this holds all the keys that were acquired by the transaction allover the cluster - backupKeyLocks: this holds all the locks for which the local node is a secondary data owner. To do: - affectedKeys belongs to LocalCacheTransaction(subclass) and no point in having it in the AbstractCacheTransaction - a better name for affectedKeys might be "clusterLockedKey" and for lockedKeys --> localLokedKeys - also add a Javadoc explaining the correlation between these key groups -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-2177?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2177: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.2.0.Final) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira