WildFly 36 Model Reference

Representation of the transaction logging storage mechanism.

Children (1)

  • transactions Represents a snapshot of the persistent information that the transaction manager stores for the purpose of recovering a transaction in the event of failure. Loading the information from the object store is provided by a 'probe' operation. The 'probe' operation flushes the existing data from the model and loads a new snapshot from the object store. The transactions model lists the transactions and provides operations to work with them. After probing, the model is updated to include information about the state of incomplete transactions. A 'stuck' transaction (one that is unable to finish) will remain in the model until either it is completed or explicitly removed using the 'delete' operation.

Attributes (2)

  • expose-all-logs Configures the behaviour of the probe operation. When true then all transaction log records are exposed. By default only a subset of the transaction log is exposed.
    • Attribute Value
    Default Value false
    Type BOOLEAN
    Nillable true
    Expressions Allowed true
    Storage runtime
    Access Type read-write
    Restart Required no-services
    Stability default
  • type Read-only attribute that specifies the implementation type of the logging store. The possible values are default, journal and jdbc.
    • Attribute Value
    Default Value default
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-only
    Stability default

Operations (3)

  • add Add a representation of the transaction logging storage mechanism.
    Request Parameter Type Required Expressions Allowed Default value Description
    type STRING false false default Read-only attribute that specifies the implementation type of the logging store. The possible values are default, journal and jdbc.
  • probe Scan the content of the transaction log and load this snapshot as content of the model under log-store resource. This operation will create a child for each pending transaction with sub-resources representing transaction participants.
  • remove Remove a representation of the transaction logging storage mechanism.