Transaction Context Support
A Broker client initiates a transaction to publish, acknowledge, or get the events that make up the transaction, then ends the transaction by committing or aborting the events. Other features of transaction context support are:
After an
ABORT operation, all request events in the transaction are discarded and will not generate reply any events, not even error replies.
All operations throw exceptions.
Any request event that generates an error following a
COMMIT operation will cause subsequent events to be discarded. Furthermore, any changes from prior events will be rolled back. If an error occurs, an exception (either
AWPR_ERROR_UNKNOWN_TRANSACTION,
AWPR_ERROR_INVALID_TRANSACTION, or
AWPR_ERROR_INVALID_CLIENT) will be thrown.
Transaction Context Timeline