Transaction Support
A Broker transactional client initiates a transaction to publish, deliver or get the events that make up the transaction, then ends the transaction by committing or aborting the events. Other features of transaction support are:
After an
ABORT operation, all request events in the transaction are discarded and will not generate any reply events, not even error replies.
All operations throw exceptions.
Any request event that generates an error on 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
BrokerTxClosedException or
BrokerInvalidTxException) will be thrown.
Transaction Context Timeline
Note:
When the Broker Server is stopped and restarted, all open transactions prior to stopping the Broker Server will be aborted.