[
https://issues.apache.org/jira/browse/ARTEMIS-5132?focusedWorklogId=940211&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-940211
]
ASF GitHub Bot logged work on ARTEMIS-5132:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Oct/24 17:26
Start Date: 25/Oct/24 17:26
Worklog Time Spent: 10m
Work Description: gemmellr opened a new pull request, #5318:
URL: https://github.com/apache/activemq-artemis/pull/5318
(no comment)
Issue Time Tracking
-------------------
Worklog Id: (was: 940211)
Remaining Estimate: 0h
Time Spent: 10m
> consolidate ActiveMQQueueLogger into ActiveMQServerLogger
> ----------------------------------------------------------
>
> Key: ARTEMIS-5132
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5132
> Project: ActiveMQ Artemis
> Issue Type: Task
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 2.39.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ActiveMQQueueLogger uses a single message ID from the middle of the range
> reserved for ActiveMQServerLogger. Different LogBundle classes should use
> their own specific code ranges. The work from ARTEMIS-5110 now ensures
> ActiveMQServerLogger cant accidentally use that code and prevents it clashing
> with ActiveMQQueueLogger for that code, but the same isnt true of other
> codes, and the reverse is not yet true.
> Rather than trying to keep them from clashing, it would be better to
> consolidate the single message from ActiveMQQueueLogger back into
> ActiveMQServerLogger where its ID belongs. This can be done without breaking
> the existing use by adding ability to define a message-specific logger name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
