[ISSUE #393] Fix DLQ Message functionality in RocketMQ Dashboard #394
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #393
What is the purpose of the change
This PR fixes multiple issues with Dead Letter Queue (DLQ) message functionality in the RocketMQ Dashboard as reported in issue #393:
Brief changelog
Backend:
DlqMessageServiceImpl.java: Implemented DLQ-specific querying usingDefaultMQPullConsumer, fixed resend to useDefaultMQProducer, added system property filtering, fixed pagination total countDlqMessageController.java: Added/resendDlqMessage.doendpoint, improved error handlingMessageController.java: FixedviewMessageto returnMessageViewdirectlyDlqMessageExcelModel.java: Added null safety checkspom.xml: Upgraded EasyExcel to 3.3.4 for Java 17 compatibilityFrontend:
dlqmessage.jsx: Fixed message detail modal, resend, export, pagination; added BornHost/BornTimestamp fieldsDlqMessageDetailViewDialog.jsx: Added BornHost and BornTimestamp displayremoteApi.js: Fixed API parameter passing and response handlingVerifying this change
All functionality manually tested:
Testing environment: RocketMQ Dashboard 2.1.1-SNAPSHOT, RocketMQ 5.3.4, Java 17, Linux