lollipopjin opened a new issue, #688: URL: https://github.com/apache/rocketmq-clients/issues/688
### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq-clients/issues) and [GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions) of this repository and believe that this is not a duplicate. - [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Programming Language of the Client Java ### Runtime Platform Environment MacOS ### RocketMQ Version of the Client/Server 5.0.6 ### Run or Compiler Version _No response_ ### Describe the Bug Should add information about transaction Source on endTransaction Request,means: 1. specify as TransactionSource.SOURCE_SERVER_CHECK when calling onRecoverOrphanedTransactionCommand(); 2. specify as TransactionSource.SOURCE_CLIENT when calling on calling transaction.rollback() or transaction.commit() ### Steps to Reproduce send a transaction message, do not rollback or commit the transaction, and waiting the server to callback for checking the transaction status. ### What Did You Expect to See? transaction soruce received in server is always the default code : SOURCE_UNSPECIFIED(0) ### What Did You See Instead? As described above: Should add information about transaction Source on endTransaction Request,means: 1. specify as TransactionSource.SOURCE_SERVER_CHECK when calling onRecoverOrphanedTransactionCommand(); 2. specify as TransactionSource.SOURCE_CLIENT when calling on calling transaction.rollback() or transaction.commit() ### Additional Context _No response_ -- 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org