8.21. Transactions and the Action Pipeline

The action pipeline is capable of running either in a transaction or by itself. To perform the former, a service must have a JCA listener attached to it with the transact property set to true. It must also be told how to retrieve the TransactionManager when running in an application server. This can be accomplished by running JNDI look-up.
When working in the action pipeline, transactions can be rolled back during the commit phase which occurs after all the onSuccess methods of the actions are called. The entire pipeline can still fail and rollback during commit phase which would cause the message to retry the pipe.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.