This repository was archived by the owner on Jun 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
I don't use aliyun #26
Labels
question
Further information is requested
Comments
What do you mean by |
自己搭建的本地mq集群,不需要认证,调用同步发送报错能得到返回值吗?
发自我的 iPhone
… 在 2019年3月19日,15:24,messense ***@***.***> 写道:
What do you mean by get the message status? If you use Producer.send_sync you can get status from its return value.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
报错会抛异常。 |
是的,是不是不支持非阿里云服务?
发自我的 iPhone
… 在 2019年3月19日,16:59,messense ***@***.***> 写道:
报错会抛异常。
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
支持的,但是目前基于 rocketmq-client-cpp 的封装在报错的时候是拿不到具体报错信息的。 |
现在同步发送拿不到返回值,报错 这个现在如何解决?
发自我的 iPhone
… 在 2019年3月19日,17:13,messense ***@***.***> 写道:
支持的,但是目前基于 rocketmq-client-cpp 的封装在报错的时候是拿不到具体报错信息的。
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
贴一下 ~/logs/rocketmq-cpp 文件夹下面最新的日志。 |
目前,使用自己搭建的非阿里云的mq服务问题比较多,
得不到发送消息的状态,并且报错,消息发送成功了,但是执行一次发送动作会发送多条一样的消息
是不是因为我把“producer.set_session_credentials('XXX', 'XXXX', 'ALIYUN')”这个认证去掉的关系?
我本地的集群不需要认证
…--
周亚亮
---------------------------------
手机:18500330983
邮件地址:zhouyaliang0622@126.com
在 2019-03-19 17:28:35,"messense" <notifications@github.com> 写道:
贴一下 ~/logs/rocketmq-cpp 文件夹下面最新的日志。
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
应该没有关系。 |
我们是自己搭建的rocketmq集群,producer.set_session_credentials('XXX', 'XXXX', 'ALIYUN')这里第三个参数可以不指定吗?,有默认值吗,如果不指定的时候,consumer消费的时候是不是也可以不指定呢? |
@afutureboss 自己搭建的 RocketMQ 集群没有配置授权机制的话可以不调用 |
Close as inactive. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I don't use aliyun,Don't need certification
How do I get the message status?
The text was updated successfully, but these errors were encountered: