Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3859

MBean for JTA transaction heuristics is imprecise

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.2.Final
    • 7.0.1.Final
    • JTA, Tooling
    • None
    • Hide

      Manually register the bean type using a system property:

      System.setProperty("com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowserHandlers",  "com.arjuna.ats.arjuna.AtomicAction=com.arjuna.ats.internal.jta.tools.osb.mbean.jta.JTAActionBean");

      Show
      Manually register the bean type using a system property: System.setProperty("com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowserHandlers",  "com.arjuna.ats.arjuna.AtomicAction=com.arjuna.ats.internal.jta.tools.osb.mbean.jta.JTAActionBean");
    • Medium
    • Hide
      MBean instrumentation for JTA record types is now registered by default.
      MBean cache is cleared before running a discovery scan (aka probing) to avoid stale data.
      Show
      MBean instrumentation for JTA record types is now registered by default. MBean cache is cleared before running a discovery scan (aka probing) to avoid stale data.
    • Done

      The app server CLI tooling for viewing transaction heuristics is imprecise because the JTSActionBean MBean isn't registered by default. The JTSActionBean is responsible for instrumenting things like the EIS product and JNDI names which is quite useful for diagnosing heuristics and other failures.

              rhn-engineering-mmusgrov Michael Musgrove
              rhn-engineering-mmusgrov Michael Musgrove
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: