[
https://issues.apache.org/jira/browse/ARTEMIS-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569076#comment-17569076
]
ASF subversion and git services commented on ARTEMIS-3896:
----------------------------------------------------------
Commit 10e1e3001cc7b3d1d7ff4764f24529f6a3db1efe in activemq-artemis's branch
refs/heads/new-logging from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=10e1e3001c ]
ARTEMIS-3896 clarify logging for transactional ops
Both audit logging and logging from the LoggingActiveMQServerPlugin are
unclear as they relate to transactional sends and acks. Both essentially
ignore the transaction which makes it appear that an operation has taken
place when, in fact, it hasn't (e.g. a transactional ack is rolled back
but the log indicates the ack went through).
This commit fix this with the following changes:
- Log details when a send or ack is added to a transaction.
- Log details when the transaction is committed.
- Log when the transaction is rolled back.
- Include transaction details in the relevant DEBUG logs.
- Simplify INFO level logging for sends & acks in
LoggingActiveMQServerPlugin. Ensure details are in the DEBUG logs.
Other changes:
- Make capitalization more consistent in a handful of audit logs.
> Clarify logging for transactional ops
> -------------------------------------
>
> Key: ARTEMIS-3896
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3896
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
