From 4cdfd8773d4f07e7c0e6150171bb1446b4833aa9 Mon Sep 17 00:00:00 2001 From: David Mueller Date: Mon, 10 Jun 2024 13:27:29 -0400 Subject: [PATCH] Update transaction-service.adoc #7385 --- modules/ROOT/pages/transaction-service.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/transaction-service.adoc b/modules/ROOT/pages/transaction-service.adoc index 5653b6b650..3af3c9c301 100644 --- a/modules/ROOT/pages/transaction-service.adoc +++ b/modules/ROOT/pages/transaction-service.adoc @@ -110,7 +110,9 @@ To store your Open Liberty transaction logs in an RDBMS, you can configure a ded ---- -The `false` value for the `transactional` attribute specifies that the datasource is non-transactional. Transaction logs can be written to this data source, but it does not participate in transactions. +The `false` value for the `transactional` attribute specifies that the data source is non-transactional. Transaction logs can be written to this data source, but it does not participate in transactions. + +When you configure a non-transactional data source to store transaction logs, you must not change the value of the `syncQueryTimeoutWithTransactionTimeout` attribute from the default, which is `false`. If you store transaction logs in an RDBMS, each server must have its own tables. You can specify a unique table suffix by using the `transactionLogDBTableSuffix` attribute for the `transaction` element. The value for this attribute is a string that is appended to the table name to make it unique to the server where the table is hosted. In the previous example, `MyServer1` is added as a suffix to any table names that are created for this server in an RDBMS.