-
Notifications
You must be signed in to change notification settings - Fork 118
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.
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
cannot find class SourceConnector #130
Comments
Caused by: java.lang.ClassNotFoundException: io.openmessaging.connector.api.source.SourceConnector |
API调用: |
The latest replicator code has been merged, you can update the code and try again. If you have any questions, please communicate in time |
same problem occurred, topics are synced while messages are not. And it could not get name server, always found name server is null. |
this question is resolved in #134 |
Do you have any other questions? |
使用了最新的master代码,消息还是不能正常在两个mq集群之间同步. |
我测试的结果:是将source mq集群 白名单设置的topic中的消息 转存到了 souce mq集群 "connect-topicname"参数设置的topic里 |
我runtime和source mq是同一个集群,target mq是另外一套,消息没同步到target mq集群里 |
同步消息的producer在初始化时连接到的是runtime使用的mq集群,消息直接同步到这个集群中 |
看代码我目前确实没找到同步到target mq集群的逻辑,看来是需要自己再实现一下了 |
这样用法是有问题的,source是需要同步的集群A,runtime配置target mq集群B, 这样A集群的topic就可以同步到B集群。 |
我按照你说的方法尝试了一下,消息是转存到了 runtime配置target mq集群B的connect-topicname里,消息并没有同步到 white-list 配置的topic中 |
Exception occurred while servicing http-request
java.lang.NoClassDefFoundError: io/openmessaging/connector/api/source/SourceConnector
The text was updated successfully, but these errors were encountered: