Ivan Bessonov created IGNITE-27587:
--------------------------------------
Summary: Connection reset exception in logs
Key: IGNITE-27587
URL: https://issues.apache.org/jira/browse/IGNITE-27587
Project: Ignite
Issue Type: Bug
Components: thin clients ai3
Reporter: Ivan Bessonov
{code:java}
2026-01-14 15:24:47:510 +0000
[WARNING][cac-dpd-cde-gg-aks-dev-0-network-worker-7][ClientInboundMessageHandler]
Exception in client connector pipeline [connectionId=899,
remoteAddress=/10.20.0.149:64660]: Connection reset
java.net.SocketException: Connection reset
at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(Unknown
Source)
at java.base/sun.nio.ch.SocketChannelImpl.read(Unknown Source)
at
io.netty.buffer.AdaptivePoolingAllocator$AdaptiveByteBuf.setBytes(AdaptivePoolingAllocator.java:1750)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1139)
at
io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:157)
at
io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.handle(AbstractNioChannel.java:445)
at
io.netty.channel.nio.NioIoHandler$DefaultNioRegistration.handle(NioIoHandler.java:388)
at
io.netty.channel.nio.NioIoHandler.processSelectedKey(NioIoHandler.java:596)
at
io.netty.channel.nio.NioIoHandler.processSelectedKeysOptimized(NioIoHandler.java:571)
at
io.netty.channel.nio.NioIoHandler.processSelectedKeys(NioIoHandler.java:512)
at io.netty.channel.nio.NioIoHandler.run(NioIoHandler.java:484)
at
io.netty.channel.SingleThreadIoEventLoop.runIo(SingleThreadIoEventLoop.java:225)
at
io.netty.channel.SingleThreadIoEventLoop.run(SingleThreadIoEventLoop.java:196)
at
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:1195)
at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Unknown Source)
{code}
This is a normal situation, there has to be no stacktrace in the logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
