[Java] Fix to use correct logger class in CompositedMessageInterceptor

[mns-one]

Problem

CompositedMessageInterceptor and MessageMeterInterceptor both implement MessageInterceptor interface

Logger in MessageMeterInterceptor was initialized with MessageMeterInterceptor.class but logger in CompositedMessageInterceptor was initialized with MessageInterceptor.class (the interface) instead of
CompositedMessageInterceptor.class
This routed all log output to the wrong logger name, making per-class log level configuration ineffective and error tracing misleading.

Changes

Replaced MessageInterceptor.class with CompositedMessageInterceptor.class

[RockteMQ-AI]

Summary

Trivial one-line fix: the logger in CompositedMessageInterceptor was incorrectly using MessageInterceptor.class (the interface) instead of CompositedMessageInterceptor.class (the actual class). This corrects the logger category for proper log filtering. LGTM.

---

Automated review by github-manager-bot

[RockteMQ-AI]

Review Summary

This PR fixes the logger class in CompositedMessageInterceptor from the interface (MessageInterceptor.class) to the implementation class (CompositedMessageInterceptor.class).

Findings

• [Warning] CompositedMessageInterceptor.java:30 — The logger was initialized with the wrong class, causing all log output to be routed to the interface's logger name instead of the implementation's. This makes per-class log level configuration ineffective and error tracing misleading.
• [Info] The fix is a simple one-line change that correctly uses CompositedMessageInterceptor.class.

Overall

Good fix for logger configuration. This is a common mistake when implementing interfaces, and it's important for debugging and log level management.

---

Automated review by RockteMQ-AI