2019-01-15 15:10:29.285 [main] INFO com.alibaba.otter.canal.deployer.CanalLauncher - ## start the canal server. 2019-01-15 15:10:40.322 [main] INFO com.alibaba.otter.canal.deployer.CanalController - ## start the canal server[10.88.26.36:11111] 2019-01-15 15:11:04.457 [main] WARN o.s.beans.GenericTypeAwarePropertyDescriptor - Invalid JavaBean property 'connectionCharset' being accessed! Ambiguous write methods found next to actually used [public void com.alibaba.otter.canal.parse.inbound.mysql.AbstractMysqlEventParser.setConnectionCharset(java.lang.String)]: [public void com.alibaba.otter.canal.parse.inbound.mysql.AbstractMysqlEventParser.setConnectionCharset(java.nio.charset.Charset)] 2019-01-15 15:11:13.807 [main] ERROR com.alibaba.druid.pool.DruidDataSource - testWhileIdle is true, validationQuery not set 2019-01-15 15:11:24.409 [main] WARN com.alibaba.druid.pool.DruidDataSource - get connection timeout retry : 1 2019-01-15 15:11:34.406 [main] INFO com.alibaba.otter.canal.deployer.CanalLauncher - ## the canal server is running now ...... 2019-01-15 15:11:34.490 [canal-instance-scan-0] INFO c.a.o.canal.deployer.monitor.SpringInstanceConfigMonitor - auto notify start example successful. 2019-01-15 15:11:36.368 [destination = im_test , address = /10.88.26.36:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> begin to find start position, it will be long time for reset or first position 2019-01-15 15:11:36.810 [destination = im_test , address = /10.88.26.36:3306 , EventParser] WARN c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - prepare to find start position just last position {"identity":{"slaveId":-1,"sourceAddress":{"address":"scm-mysql-testdb01.baozun.com","port":3306}},"postion":{"gtid":"","included":false,"journalName":"mysql-bin.000515","position":8367859,"serverId":200,"timestamp":1547536126000}} 2019-01-15 15:12:24.646 [Thread-7] INFO com.alibaba.otter.canal.deployer.CanalLauncher - ## stop the canal server 2019-01-15 15:12:33.663 [Thread-8] INFO com.alibaba.otter.canal.kafka.CanalKafkaProducer - ## stop the kafka producer 2019-01-15 15:12:33.677 [Thread-7] WARN c.a.o.c.common.zookeeper.running.ServerRunningMonitor - canal is running in node[1] , but not in node[1] 2019-01-15 15:12:33.677 [Thread-7] WARN c.a.o.c.common.zookeeper.running.ServerRunningMonitor - canal is running in node[1] , but not in node[1] 2019-01-15 15:12:36.415 [Thread-8] INFO com.alibaba.otter.canal.kafka.CanalKafkaProducer - ## kafka producer is down. 2019-01-15 15:12:36.443 [Thread-7] WARN c.a.o.c.common.zookeeper.running.ServerRunningMonitor - canal is running in node[1] , but not in node[1] 2019-01-15 15:12:36.443 [Thread-7] WARN c.a.o.c.common.zookeeper.running.ServerRunningMonitor - canal is running in node[1] , but not in node[1]
原提问者GitHub用户ZSH9053
将conf/canal.properties文件中的这一行注释掉 #canal.instance.tsdb.spring.xml = classpath:spring/tsdb/h2-tsdb.xml
原回答者GitHub用户midonghao
看起来这个错误是由于Canal启动时出现了一些JavaBean属性的问题。具体来说,Canal在尝试设置一个名为connectionCharset的属性时,遇到了多个可能的写方法,导致出现了歧义。这可能是由于Canal中的某些类或配置文件与您的环境不兼容所导致的。
处理这个问题的方法可能有很多种,具体取决于您的环境和Canal的版本。以下是一些可能有用的步骤:
确保您使用的是最新版本的Canal。在Canal的GitHub仓库中,您可以找到最新的代码和发布版本。升级到最新版本可能会修复一些已知的问题和错误。
检查您的Java版本是否与Canal的要求相匹配。在Canal的文档中,您可以找到Canal所需的Java版本和其他要求。如果您使用的是不受支持的Java版本,可能会导致一些问题。
检查Canal所需的依赖项是否正确安装。在Canal的文档中,您可以找到Canal所需的依赖项和版本。确保这些依赖项已正确安装,并且与Canal的版本兼容。
检查您的配置文件是否正确。在Canal的文档中,您可以找到有关如何配置Canal的信息。确保您的配置文件中没有任何错误,并且与您的环境相匹配。
版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。