Canal在window下的报错处理，ERROR java.net.SocketException: Socket already closed

最新推荐文章于 2024-08-12 12:23:55 发布

XinShun

最新推荐文章于 2024-08-12 12:23:55 发布

阅读量3.5k

点赞数 1

分类专栏： MySQL C#开发

本文链接：https://blog.csdn.net/XinShun/article/details/100533663

版权

C#开发同时被 2 个专栏收录

52 篇文章 0 订阅

订阅专栏

MySQL

5 篇文章 0 订阅

订阅专栏

1、报错内容

 at java.lang.Thread.run(Unknown Source) [na:1.8.0_131]
2019-09-04 10:17:26.503 [destination = example , address = /127.0.0.1:3306 , EventParser] 
ERROR com.alibaba.otter.canal.common.alarm.LogAlarmHandler - destination:example[com.alibaba.otter.canal.parse.exception.CanalParseException: 
java.net.SocketException: Socket already closed.
Caused by: java.net.SocketException: Socket already closed.
        at com.alibaba.otter.canal.parse.driver.mysql.socket.BioSocketChannel.write(BioSocketChannel.java:39)
        at com.alibaba.otter.canal.parse.driver.mysql.utils.PacketManager.writeBody0(PacketManager.java:47)
        at com.alibaba.otter.canal.parse.driver.mysql.utils.PacketManager.writeBody(PacketManager.java:40)
        at com.alibaba.otter.canal.parse.driver.mysql.MysqlQueryExecutor.query(MysqlQueryExecutor.java:55)
        at com.alibaba.otter.canal.parse.inbound.mysql.MysqlConnection.query(MysqlConnection.java:106)
        at com.alibaba.otter.canal.parse.inbound.mysql.MysqlConnection.loadBinlogFormat(MysqlConnection.java:469)
        at com.alibaba.otter.canal.parse.inbound.mysql.MysqlConnection.getBinlogFormat(MysqlConnection.java:643)
        at com.alibaba.otter.canal.parse.inbound.mysql.MysqlEventParser.preDump(MysqlEventParser.java:92)
        at com.alibaba.otter.canal.parse.inbound.AbstractEventParser$3.run(AbstractEventParser.java:175)
        at java.lang.Thread.run(Unknown Source)

2、运行CanalSharp-master中的CanalSharp.SimpleClient报：

CanalSharp.Protocol.Exception.CanalClientException:“failed to subscribe with reason: 
something goes wrong with channel:[id: 0x632f3ee6, /192.168.2.190:60241 => 
/192.168.2.190:11111], 
exception=com.alibaba.otter.canal.server.exception.CanalServerException: 
destination:example should start first”

3、我的问题是因为在启动时“以管理员身份运行”了

4、直接双击startup.bat启动（不要以管理员身份运行)

2019-09-04 10:22:30.528 [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-09-04 10:22:30.679 [main] ERROR com.alibaba.druid.pool.DruidDataSource - testWhileIdle is true, validationQuery not set
2019-09-04 10:22:30.862 [main] WARN  c.a.o.canal.parse.inbound.mysql.dbsync.LogEventConvert - --> init table filter : ^.*\..*$
2019-09-04 10:22:30.862 [main] WARN  c.a.o.canal.parse.inbound.mysql.dbsync.LogEventConvert - --> init table black filter :
2019-09-04 10:22:30.907 [destination = example , address = /127.0.0.1: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-09-04 10:22:30.935 [main] WARN  c.a.o.canal.parse.inbound.mysql.dbsync.LogEventConvert - --> init table filter : ^.*\..*$
2019-09-04 10:22:30.946 [destination = example , address = /127.0.0.1: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":"fiddler","port":3306}},"postion":{"gtid":"","included":false,"journalName":"mysql-bin.000003","position":1589,"serverId":1,"timestamp":1567563278000}}
2019-09-04 10:22:31.122 [destination = example , address = /127.0.0.1:3306 , EventParser] WARN  c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> find start position successfully, EntryPosition[included=false,journalName=mysql-bin.000003,position=1589,serverId=1,gtid=,timestamp=1567563278000] cost : 209ms , the next step is binlog dump

5、运行CanalSharp-master中的CanalSharp.SimpleClient，成功

6、显示结果