WildFly Full 27 Model Reference

  1. home
  2. subsystem=transactions
  3. log-store=log-store
  4. transactions
  5. participants

The resource that did work in a transaction.

Attributes (6)

  • eis-product-name The Jakarta Connectors enterprise information system's product name.
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • eis-product-version The Jakarta Connectors enterprise information system's product version.
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • jmx-name The JMX name of this participant.
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • jndi-name JNDI name of this participant.
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • status Reports the commitment status of this participant (can be one of Pending, Prepared, Failed, Heuristic or Readonly).
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-only
    Allowed Values PENDING
    PREPARED
    FAILED
    HEURISTIC
    READONLY
  • type The type name under which this record is stored.
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-only

Operations (3)

  • delete Attempt to remove this participant from its containing transaction log. If the participant is an XA resource an attempt will be made to call forget on the actual resource and if the forget call fails then the remove operation will also fail.
  • recover If this record is in a heuristic state then attempt to replay the commit phase of the 2PC transaction. It switches the 'HEURISTIC' participant status to 'PREPARED', the operation does not immediately start the recovery process but the recovery manager will consider this participant with 'PREPARED' status in the next cycle.
  • refresh Refresh the management view of the attributes of this participant record by querying the transaction log which will update the snapshot view loaded in the model. Note that the model contains only a snapshot view of the transactions from time the probe was executed, not the real-time data from the transaction log, hence the need for this refresh operation.