This is an automated email from the ASF dual-hosted git repository.
vongosling pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/rocketmq.git
The following commit(s) were added to refs/heads/develop by this push:
new fcc20de [ISSUE #3059] typo transactional message wiki
fcc20de is described below
commit fcc20dee22d92d4cf0cdba5db21e0de1663478a5
Author: yumingyue98 <[email protected]>
AuthorDate: Sat Jun 26 14:34:53 2021 +0800
[ISSUE #3059] typo transactional message wiki
Co-authored-by: yumingyue98 <[email protected]>
---
docs/en/Example_Transaction.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/en/Example_Transaction.md b/docs/en/Example_Transaction.md
index a35b040..5d1cff9 100644
--- a/docs/en/Example_Transaction.md
+++ b/docs/en/Example_Transaction.md
@@ -89,7 +89,7 @@ public class TransactionListenerImpl implements
TransactionListener {
## 3 Usage Constraint
1. Messages of the transactional have no schedule and batch support.
2. In order to avoid a single message being checked too many times and lead to
half queue message accumulation, we limited the number of checks for a single
message to 15 times by default, but users can change this limit by change the
```transactionCheckMax``` parameter in the configuration of the broker, if one
message has been checked over ```transactionCheckMax``` times, broker will
discard this message and print an error log at the same time by default. Users
can change this behav [...]
-3. A transactional message will be checked after a certain period of time that
determined by parameter g```transactionTimeout``` in the configuration of the
broker. And users also can change this limit by set user property
```CHECK_IMMUNITY_TIME_IN_SECONDS``` when sending transactional message, this
parameter takes precedence over the ```transactionTimeout``` parameter.
+3. A transactional message will be checked after a certain period of time that
determined by parameter ```transactionTimeout``` in the configuration of the
broker. And users also can change this limit by set user property
```CHECK_IMMUNITY_TIME_IN_SECONDS``` when sending transactional message, this
parameter takes precedence over the ```transactionTimeout``` parameter.
4. A transactional message maybe checked or consumed more than once.
5. Committed message reput to the user’s target topic may fail. Currently, it
depends on the log record. High availability is ensured by the high
availability mechanism of RocketMQ itself. If you want to ensure that the
transactional message isn’t lost and the transaction integrity is guaranteed,
it is recommended to use synchronous double write. mechanism.
6. Producer IDs of transactional messages cannot be shared with producer IDs
of other types of messages. Unlike other types of message, transactional
messages allow backward queries. MQ Server query clients by their Producer IDs.
