io.quarkus.narayana.jta.runtime.TransactionManagerBuildTimeConfig.jdp Maven / Gradle / Ivy
Show all versions of quarkus-narayana-jta Show documentation
io.quarkus.narayana.jta.runtime.TransactionManagerBuildTimeConfig.ALLOW=Allow using multiple XA unaware resources in the same transactional demarcation.\n\nThis will log a warning once on application startup,\nbut not on each use of multiple XA unaware resources in the same transactional demarcation.
io.quarkus.narayana.jta.runtime.TransactionManagerBuildTimeConfig.FAIL=Allow using multiple XA unaware resources in the same transactional demarcation,\nbut log a warning on each occurrence.
io.quarkus.narayana.jta.runtime.TransactionManagerBuildTimeConfig.WARN_EACH=Allow using multiple XA unaware resources in the same transactional demarcation,\nbut log a warning on each occurrence.
io.quarkus.narayana.jta.runtime.TransactionManagerBuildTimeConfig.WARN_FIRST=Allow using multiple XA unaware resources in the same transactional demarcation,\nbut log a warning on the first occurrence.
io.quarkus.narayana.jta.runtime.TransactionManagerBuildTimeConfig.unsafeMultipleLastResources=Define the behavior when using multiple XA unaware resources in the same transactional demarcation.\n
\nDefaults to {@code fail}.\n{@code warn-each}, {@code warn-first}, and {@code allow} are UNSAFE and should only be used for compatibility.\nEither use XA for all resources if you want consistency, or split the code into separate\nmethods with separate transactions.\n
\nNote that using a single XA unaware resource together with XA aware resources, known as\nthe Last Resource Commit Optimization (LRCO), is different from using multiple XA unaware\nresources. Although LRCO allows most transactions to complete normally, some errors can\ncause an inconsistent transaction outcome. Using multiple XA unaware resources is not\nrecommended since the probability of inconsistent outcomes is significantly higher and\nmuch harder to recover from than LRCO. For this reason, use LRCO as a last resort.\n
\nWe do not recommend using this configuration property, and we plan to remove it in the future,\nso you should plan fixing your application accordingly.\nIf you think your use case of this feature is valid and this option should be kept around,\nopen an issue in our tracker explaining why.\n\n@deprecated This property is planned for removal in a future version.