[ https://issues.jboss.org/browse/AS7-4331?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-4331: ----------------------------- Fix Version/s: 7.2.0.Alpha1 (was: 7.1.2.Final-redhat1) -- 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/AS7-4331?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-4331: ----------------------------- Fix Version/s: 7.2.0.Alpha1 (was: 7.1.3.Final (EAP)) -- 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/AS7-4331?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-4331: ----------------------------- Fix Version/s: No Release (was: 7.2.0.Alpha1) -- 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/AS7-4331?page=com.atlassian.jira.plugin.s... ] Michael Musgrove reassigned AS7-4331: ------------------------------------- Assignee: Stefano Maestri (was: Michael Musgrove) -- 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/AS7-4331?page=com.atlassian.jira.plugin.s... ] Michael Musgrove edited comment on AS7-4331 at 8/22/12 11:30 AM: ----------------------------------------------------------------- There are 2 use cases: 1. Enable/disable statistics and provide an indication of the current status of this property (note that statistics are displayed in the web console but we cannot enable/disable them from it) 2. Browsing and Manipulating transaction logs: The model node for transaction logs is log-store which provides an operation called "probe" which reads the transaction logs and creates a node for each one. *This operation needs to be exposed in the web console A transaction node: - provides an operation called "delete" for removing the transaction log; - provides attributes which describe the log entry; - contains a child resource called "participants" *Each of these last three items needs to be exposed in the web console *Transaction nodes and their participants need to be exposed in the web console [Note it is normal for transaction logs to come and go whenever the transaction manager is running - the only way to get a current snapshot of which logs are present is by re-issuing the "probe" operation]. The "participants" child resource contains nodes representing each prepared transaction participant. Participant nodes: - contain attributes describing the resource such as its jndi name, its EIS product name and version, its status etc (use :read-resource in the CLI to see these values); - contain two operations, "recover" and "refresh". If the status is "HEURISTIC" then the refresh operation will change the state back to "PREPARE" and trigger a recovery attempt. In the case of a heuristic participant the recover operation will (try) to cause the commit operation to be replayed (and if successful the participant will be removed from the log). *Each of these last two items needs to be exposed in the web console Note also that fixing the linked jira (JBPAPP-8816) will expose all log records and these should be exposed too (under the control of a check box/button for "advance" mode). was (Author: mmusgrov): There are 2 use cases: 1. Enable/disable statistics and provide an indication of the current status of this property 2. Browsing and Manipulating transaction logs: The model node for transaction logs is log-store which provides an operation called "probe" which reads the transaction logs and creates a node for each one. *This operation needs to be exposed in the web console A transaction node: - provides an operation called "delete" for removing the transaction log; - provides attributes which describe the log entry; - contains a child resource called "participants" *Each of these last three items needs to be exposed in the web console *Transaction nodes and their participants need to be exposed in the web console [Note it is normal for transaction logs to come and go whenever the transaction manager is running - the only way to get a current snapshot of which logs are present is by re-issuing the "probe" operation]. The "participants" child resource contains nodes representing each prepared transaction participant. Participant nodes: - contain attributes describing the resource such as its jndi name, its EIS product name and version, its status etc (use :read-resource in the CLI to see these values); - contain two operations, "recover" and "refresh". If the status is "HEURISTIC" then the refresh operation will change the state back to "PREPARE" and trigger a recovery attempt. In the case of a heuristic participant the recover operation will (try) to cause the commit operation to be replayed (and if successful the participant will be removed from the log). *Each of these last two items needs to be exposed in the web console Note also that fixing the linked jira (JBPAPP-8816) will expose all log records and these should be exposed too (under the control of a check box/button for "advance" mode). -- 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