[
https://issues.apache.org/jira/browse/ARTEMIS-4459?focusedWorklogId=885092&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-885092
]
ASF GitHub Bot logged work on ARTEMIS-4459:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Oct/23 15:27
Start Date: 13/Oct/23 15:27
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4648:
URL:
https://github.com/apache/activemq-artemis/pull/4648#issuecomment-1761705687
The main details in the new logging are the MQTT client ID as well as the ID
for the MQTT `PUBLISH` packet. Neither of these will be available in the audit
log. You'd need MQTT protocol logging (i.e. `TRACE` on
`org.apache.activemq.artemis.core.protocol.mqtt.MQTTUtil`) to be active. I
considered putting this new logging on that same logger, but ultimately I
didn't. What do you think about using the same logger as the protocol trace?
Thinking about it more now it seems like a natural fit.
Issue Time Tracking
-------------------
Worklog Id: (was: 885092)
Time Spent: 0.5h (was: 20m)
> Broker should log when ignoring a duplicate MQTT QoS 2 message
> --------------------------------------------------------------
>
> Key: ARTEMIS-4459
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4459
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
