Skip to content

Question about connecting  Aliware MQ. #121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
messense opened this issue Mar 20, 2019 · 2 comments
Closed

Question about connecting  Aliware MQ. #121

messense opened this issue Mar 20, 2019 · 2 comments
Labels
help wanted Extra attention is needed
Milestone
1.2.2

Comments

@messense
Copy link
Member

https://help.aliyun.com/document_detail/102895.html?spm=5176.ons.ClientManagement.2.12be6c5caayp7K#20190116.1

Producer 报错日志：

[2019-Mar-20 17:04:42.658904](info):m_tcpConnectTimeout:3000, m_tcpTransportTryLockTimeout:3, m_pullThreadNum:12
[2019-Mar-20 17:04:42.659166](info):MQClient start,groupname:CID-kg-data-sync,clientID:24453-30.17.224.62@DEFAULT,instanceName:DEFAULT,nameserveraddr:MQ_INST_1730073665186091_Bae8Titg.mq-internet-access.mq-internet.aliyuncs.com:80
[2019-Mar-20 17:04:42.659202](info):DefaultMQProducer:CID-kg-data-sync start
[2019-Mar-20 17:04:42.659199](info):TcpRemotingClient::boost asio async service runing
[2019-Mar-20 17:04:42.659241](info):update Namesrv:MQ_INST_1730073665186091_Bae8Titg.mq-internet-access.mq-internet.aliyuncs.com:80
[2019-Mar-20 17:04:42.659283](info):user specfied name server address: MQ_INST_1730073665186091_Bae8Titg.mq-internet-access.mq-internet.aliyuncs.com:80
[2019-Mar-20 17:04:42.659308](info):MQClientFactory:24453-30.17.224.62@DEFAULT start
[2019-Mar-20 17:04:42.659350](warning):sendheartbeat brokeradd is empty
[2019-Mar-20 17:04:42.659418](info):start scheduled task:24453-30.17.224.62@DEFAULT
[2019-Mar-20 17:04:42.671387](warning):sendheartbeat brokeradd is empty
[2019-Mar-20 17:04:45.664350](info):updateTopicRouteInfoFromNameServer start:TBW102
[2019-Mar-20 17:04:45.664729](info):namesrvIndex is:1, index:0, namesrvaddrlist size:1
[2019-Mar-20 17:04:45.667634](info):try to connect to fd:23, addr:MQ_INST_1730073665186091_Bae8Titg.mq-internet-access.mq-internet.aliyuncs.com
[2019-Mar-20 17:04:45.667754](info):Wait till event base is looping
[2019-Mar-20 17:04:45.667793](info):Notify on event_base_dispatch
[2019-Mar-20 17:04:45.667924](info):eventcb: received event:80 on fd:23
[2019-Mar-20 17:04:45.667984](info):eventcb:connect to fd:23 successfully
[2019-Mar-20 17:04:45.668032](info):received libevent callback event
[2019-Mar-20 17:04:49.669743](info):connect timeout
[2019-Mar-20 17:04:49.669884](info):connect server with addr:MQ_INST_1730073665186091_Bae8Titg.mq-internet-access.mq-internet.aliyuncs.com:80 success
[2019-Mar-20 17:05:12.673456](warning):sendheartbeat brokeradd is empty
[2019-Mar-20 17:05:15.663867](info):updateTopicRouteInfoFromNameServer start:TBW102
[2019-Mar-20 17:05:29.833375](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:29.858696](info):updateTopicRouteInfoFromNameServer has data
[2019-Mar-20 17:05:29.858795](info):updateTopicRouteInfoFromNameServer changed:
[2019-Mar-20 17:05:29.858889](info):updateTopicRouteInfoFromNameServer with default
[2019-Mar-20 17:05:29.858940](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:29.880740](warning):tryToFindTopicPublishInfo null:
[2019-Mar-20 17:05:29.880816](warning):Retry many times, still failed
[2019-Mar-20 17:05:29.880847](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:29.917073](info):updateTopicRouteInfoFromNameServer has data
[2019-Mar-20 17:05:29.917208](info):updateTopicRouteInfoFromNameServer changed:
[2019-Mar-20 17:05:29.917340](info):updateTopicRouteInfoFromNameServer with default
[2019-Mar-20 17:05:29.917410](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:29.935410](warning):tryToFindTopicPublishInfo null:
[2019-Mar-20 17:05:29.935541](warning):Retry many times, still failed
[2019-Mar-20 17:05:29.935608](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:29.955637](info):updateTopicRouteInfoFromNameServer has data
[2019-Mar-20 17:05:29.955777](info):updateTopicRouteInfoFromNameServer changed:
[2019-Mar-20 17:05:29.955925](info):updateTopicRouteInfoFromNameServer with default
[2019-Mar-20 17:05:29.956007](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:29.976046](warning):tryToFindTopicPublishInfo null:
[2019-Mar-20 17:05:29.976179](warning):Retry many times, still failed
[2019-Mar-20 17:05:29.976247](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:30.002507](info):updateTopicRouteInfoFromNameServer has data
[2019-Mar-20 17:05:30.002629](info):updateTopicRouteInfoFromNameServer changed:
[2019-Mar-20 17:05:30.002705](info):updateTopicRouteInfoFromNameServer with default
[2019-Mar-20 17:05:30.002743](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:30.023208](warning):tryToFindTopicPublishInfo null:
[2019-Mar-20 17:05:30.023299](warning):Retry many times, still failed
[2019-Mar-20 17:05:30.023341](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:30.043084](info):updateTopicRouteInfoFromNameServer has data
[2019-Mar-20 17:05:30.043142](info):updateTopicRouteInfoFromNameServer changed:
[2019-Mar-20 17:05:30.043200](info):updateTopicRouteInfoFromNameServer with default
[2019-Mar-20 17:05:30.043225](info):updateTopicRouteInfoFromNameServer start:
[2019-Mar-20 17:05:30.062510](warning):tryToFindTopicPublishInfo null:
[2019-Mar-20 17:05:30.062630](warning):Retry many times, still failed
[2019-Mar-20 17:05:30.062778](error):msg: No route info of this topic:
@du-do
Copy link

du-do commented Mar 21, 2019 •
edited
Loading

我试了下，感觉像是不支持。用公有云SDK通过log发现topic和GID都在前面拼接了实例ID。但是即使我使用拼接后的GID和topic也不行，NAMESRV_ADDR不知道要如何对应。
以下是我截取的公有云SDK发送消息时的日志，配置的topic是TestAlimq，GID是GID-test
03/20/19 09:21:30:634.015 INFO 140332159832000 - Group name :GID-test[DefaultMQProducer.cpp:70] 03/20/19 09:21:30:635.184 INFO 140332159832000 - new Group name:MQ_INST_1452639447256576_BabFsdtU%GID-test[DefaultMQProducer.cpp:73] 03/20/19 09:21:30:639.010 INFO 140332159832000 - updateTopicRouteInfoFromNameServer start:MQ_INST_1452639447256576_BabFsdtU%TestAlimq[MQClientFactory.cpp:176]

@ShannonDing ShannonDing added this to the 1.2.3 milestone Mar 21, 2019
@ShannonDing ShannonDing changed the title 是否支持阿里云资源隔离 MQ 实例？ Question about connecting  Aliware MQ. Mar 21, 2019
@ShannonDing ShannonDing added the help wanted Extra attention is needed label Mar 21, 2019
@ShannonDing
Copy link
Member

Scheduled to be available in the next release version.

@messense messense mentioned this issue Apr 2, 2019
Closed
@ShannonDing ShannonDing mentioned this issue Apr 15, 2019
Merged
5 tasks
ShannonDing added a commit that referenced this issue Apr 17, 2019
@ShannonDing
[ISSUE #121]Support connect MQ endpoint with ACL (#133)
28c4cf0 
* Add function name and line in the log format

* Support connect aliyun endpoint

* Modify signature context to link aliyun mq

* Format NameSpace file

* Format file style

* Update MQClientFactory.cpp

* Remove unnecessary comments
@ShannonDing ShannonDing modified the milestones: 1.2.3, 1.2.2 Apr 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
1.2.2
Development

No branches or pull requests
3 participants
@messense @ShannonDing @du-do