Closed Xdydy closed 1 year ago
The user ID needs to be specified on the HTTP request header, which can be specified by connecting to the internal user account system. We will make an optimization later here. If it is not specified, the built-in default account ID will be used.
Content-Type:application/json
resourceOwnerAccountId:${AccountId}
parentAccountId:${AccountId}
loginAccountId:${AccountId}
The user ID needs to be specified on the HTTP request header, which can be specified by connecting to the internal user account system. We will make an optimization later here. If it is not specified, the built-in default account ID will be used.
Content-Type:application/json resourceOwnerAccountId:${AccountId} parentAccountId:${AccountId} loginAccountId:${AccountId}
Thanks for your reply. After trying that my "access.log" has received the request info. However I met the new issue that the rocketmq-eventbridge.log reminds me that
@@ERROR@@o.a.r.e.a.p.d.r.r.RocketMQMetaService[52]@@Create topic failed.
org.apache.rocketmq.client.exception.MQClientException: create new topic failed
and the http response returns that
{
"requestId": "6eed022f-2429-426f-8c72-559347af1bf1",
"code": "InternalError",
"message": "InternalError"
}
Can you explain why?
Please give the details of the stack. According to the existing exceptions, there may be an exception in the connection between EB and RMQ, or there may be an exception in the deployed RMQ.
I close this question, and the new question can recreate an Issue.
When I write the EventBridge demo
It responses as follows: