chennaji9 opened a new pull request, #11313:
URL: https://github.com/apache/rocketmq/pull/11313
<!-- Please make sure the target branch is right. In most case, the target
branch should be `develop`. -->
### Which Issue(s) This PR Fixes
Fixes #11312
### Brief Description
The "enable message trace" snippets in `docs/en/Operations_Trace.md`
(sections 4.1 and 4.2) constructed `DefaultMQProducer("ProducerGroupName",
true)` and `DefaultMQPushConsumer("CID_JODIE_1", true)`. No `(String, boolean)`
constructor exists for either class — the trace-enabling constructors take
`(String producerGroup/consumerGroup, boolean enableMsgTrace, String
customizedTraceTopic)`. Copying the snippets verbatim fails to compile (`The
constructor DefaultMQProducer(String, boolean) is undefined`).
Both snippets now pass `null` as `customizedTraceTopic` (keep the default
system trace topic), matching the three-argument form that section 4.3 of the
same page already shows for a custom trace topic. Two-line change, single file.
### How Did You Test This Change?
Static API verification, no runtime behavior involved (documentation-only
change):
- `mvn -pl client -am -DskipTests compile` → BUILD SUCCESS on JDK 11, then
`javap -classpath client/target/classes` on both classes confirms the
constructor set — `(String, boolean)` is absent and `(String, boolean, String)`
is the trace constructor (`DefaultMQProducer.java:280`,
`DefaultMQPushConsumer.java:336`).
- `null` for `customizedTraceTopic` is the documented "use default trace
topic" value in both constructors' Javadoc.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
