3.4.7.11 Export Transaction Failure

The Export Transaction Failure event MUST be signaled with the following arguments:

  • A transaction object.

  • A value indicating the failure reason. The reason MUST be set to one of the following values:

    • Log Full

    • No Mem

    • Too Late

    • Too Many

    • Comm Failed

If the Export Transaction Failure event is signaled, the transaction manager MUST perform the following actions:

  • Find an instance of a CONNTYPE_TXUSER_EXPORT2 (section 2.2.8.2.2.3) connection in the provided transaction's connection list.

    • Send the matching message for the following reason codes:

      • Log Full: TXUSER_EXPORT_MTAG_EXPORT_LOG_FULL (section 2.2.8.2.2.2.7)

      • No Mem: TXUSER_EXPORT_MTAG_EXPORT_NO_MEM (section 2.2.8.2.2.2.8)

      •  Too Late: TXUSER_EXPORT_MTAG_EXPORT_TOO_LATE (section 2.2.8.2.2.2.9)

      • Too Many: TXUSER_EXPORT_MTAG_EXPORT_TOO_MANY (section 2.2.8.2.2.2.10)

      • Not Found: TXUSER_EXPORT_MTAG_EXPORT_TX_NOT_FOUND (section 2.2.8.2.2.2.11)

      • Comm Failed: TXUSER_EXPORT_MTAG_EXPORT_COMM_FAILED (section 2.2.8.2.2.3.1)

    • Set the connection state to Ended.

  • Otherwise, find an instance of a CONNTYPE_TXUSER_EXPORT (section 2.2.8.2.2.2) connection in the provided transaction's connection list.

    • Send the matching message for the following reason codes:

      • Log Full: TXUSER_EXPORT_MTAG_EXPORT_LOG_FULL (section 2.2.8.2.2.2.7)

      • No Mem: TXUSER_EXPORT_MTAG_EXPORT_NO_MEM (section 2.2.8.2.2.2.8)

      •  Too Late: TXUSER_EXPORT_MTAG_EXPORT_TOO_LATE (section 2.2.8.2.2.2.9)

      • Too Many: TXUSER_EXPORT_MTAG_EXPORT_TOO_MANY (section 2.2.8.2.2.2.10)

      • Not Found: TXUSER_EXPORT_MTAG_EXPORT_TX_NOT_FOUND (section 2.2.8.2.2.2.11)

  • Otherwise, if no such connection exists, the event MUST be ignored.