Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6229

System Failures in Transactions subsystem runtime view doesn't show number-of-system-rollbacks

    Details

    • Type: Bug
    • Status: Verified (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 7.1.0.DR6
    • Component/s: Web Console
    • Labels:
      None
    • Target Release:
    • Steps to Reproduce:
      Hide
      1. start EAP in standalone mode with standalone-full-ha configuration
      2. enable statistics for transaction subsystem
      3. reload
      4. make some EJB calls which enforce rollback
      5. using web console navigate to Runtime > Standalone Server > Subsystems > Transactions > View
      Show
      start EAP in standalone mode with standalone-full-ha configuration enable statistics for transaction subsystem reload make some EJB calls which enforce rollback using web console navigate to Runtime > Standalone Server > Subsystems > Transactions > View

      Description

      /subsystem=transactions:read-attribute(name=number-of-system-rollbacks)

      {
          "outcome" => "success",
          "result" => 0L
      }
      

      /subsystem=transactions:read-resource(include-runtime=true)

      {
          "outcome" => "success",
          "result" => {
              "average-commit-time" => 12652L,
              "default-timeout" => 300,
              "enable-statistics" => false,
              "enable-tsm-status" => false,
              "hornetq-store-enable-async-io" => false,
              "jdbc-action-store-drop-table" => false,
              "jdbc-action-store-table-prefix" => undefined,
              "jdbc-communication-store-drop-table" => false,
              "jdbc-communication-store-table-prefix" => undefined,
              "jdbc-state-store-drop-table" => false,
              "jdbc-state-store-table-prefix" => undefined,
              "jdbc-store-datasource" => undefined,
              "journal-store-enable-async-io" => false,
              "jts" => false,
              "node-identifier" => "1",
              "number-of-aborted-transactions" => 1L,
              "number-of-application-rollbacks" => 1L,
              "number-of-committed-transactions" => 3L,
              "number-of-heuristics" => 0L,
              "number-of-inflight-transactions" => 0L,
              "number-of-nested-transactions" => 0L,
              "number-of-resource-rollbacks" => 0L,
              "number-of-system-rollbacks" => 0L,
              "number-of-timed-out-transactions" => 0L,
              "number-of-transactions" => 4L,
              "object-store-path" => "tx-object-store",
              "object-store-relative-to" => "jboss.server.data.dir",
              "process-id-socket-binding" => undefined,
              "process-id-socket-max-ports" => 10,
              "process-id-uuid" => true,
              "recovery-listener" => false,
              "socket-binding" => "txn-recovery-environment",
              "statistics-enabled" => false,
              "status-socket-binding" => "txn-status-manager",
              "use-hornetq-store" => false,
              "use-jdbc-store" => false,
              "use-journal-store" => false,
              "commit-markable-resource" => undefined,
              "log-store" => {"log-store" => undefined}
          }
      }
      

      Compare with provided txt_system_failures.png screenshot.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  claudio4j Claudio Miranda
                  Reporter:
                  pjelinek Pavel Jelinek
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: