[ARTEMIS-5132] consolidate ActiveMQQueueLogger into ActiveMQServerLogger

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.39.0
• Labels: pull-request-available
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 25/Oct/24 17:16
• Updated: 29/Oct/24 16:51
• Resolved: 29/Oct/24 10:06

Description

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.

Issue Links

• links to: GitHub Pull Request #5318