neo4j出现bug,不知原因,debug日志一直循环打印,Connection reset by peer
发布于 13 天前 作者 daydayup 104 次浏览 来自 问答

多台neo4j,应用不同业务,但是昨天几台neo4j的debug.log文件,突然出现一下报错信息,并一直循环,已经持续2天了。 有一台测试用的neo4j,已确认没有外部服务调用它,但是也同样debug.log持续报错。 又遇到过的大佬,帮一起看下。

2018-10-31 02:53:31.104+0000 WARN [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. Connection reset by peer java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:192) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288) at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1100) at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:367) at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:118) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:642) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565) at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858) at java.lang.Thread.run(Thread.java:745)

5 回复

每时每刻一直在循环报错,持续十天了

2018-11-07 09:10:15.871+0000 INFO [o.n.k.i.p.Procedures] tx is null, either the other transaction finished gracefully or has not yet been start. 2018-11-07 09:10:16.054+0000 WARN [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. syscall:read(…) failed: Connection reset by peer io.netty.channel.unix.Errors$NativeIoException: syscall:read(…) failed: Connection reset by peer at io.netty.channel.unix.FileDescriptor.readAddress(…)(Unknown Source) 2018-11-07 09:10:16.159+0000 WARN [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. syscall:read(…) failed: Connection reset by peer io.netty.channel.unix.Errors$NativeIoException: syscall:read(…) failed: Connection reset by peer at io.netty.channel.unix.FileDescriptor.readAddress(…)(Unknown Source) 2018-11-07 09:10:16.865+0000 WARN [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. syscall:read(…) failed: Connection reset by peer io.netty.channel.unix.Errors$NativeIoException: syscall:read(…) failed: Connection reset by peer at io.netty.channel.unix.FileDescriptor.readAddress(…)(Unknown Source) 2018-11-07 09:10:17.149+0000 WARN [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. syscall:read(…) failed: Connection reset by peer io.netty.channel.unix.Errors$NativeIoException: syscall:read(…) failed: Connection reset by peer at io.netty.channel.unix.FileDescriptor.readAddress(…)(Unknown Source) 2018-11-07 09:10:17.222+0000 WARN [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. syscall:read(…) failed: Connection reset by peer io.netty.channel.unix.Errors$NativeIoException: syscall:read(…) failed: Connection reset by peer

neo4j 的 debug.log日志文件,持续报错。

网络连接被重置,就是网络异常,检查下网络,比如防火墙,网关 等

@pangguoming 感谢回答。 但是应该不是网络问题,因为,业务还能正常访问,neo4j库还正常,但是这个日志持续不断在打印,网络应该不会这么频繁持续的抖动的。

回到顶部