[ 
https://issues.apache.org/jira/browse/IGNITE-24813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-24813:
------------------------------------
    Description: 
In case of a server connection loss (node goes down, network issue, etc) the 
following warning appears in *client log*:

{code}
[2025-03-17T11:44:52,986][WARN ][nioEventLoopGroup-9-1][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.
 java.net.SocketException: Connection reset
        at 
java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:401)
 ~[?:?]
        at 
java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:434) ~[?:?]
        at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255) 
~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
        at 
io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) 
~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
        at io.netty.buffer.WrappedByteBuf.writeBytes(WrappedByteBuf.java:821) 
~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
        at 
io.netty.buffer.AdvancedLeakAwareByteBuf.writeBytes(AdvancedLeakAwareByteBuf.java:636)
 ~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
{code}

Improve exception handling and log a better warning (which endpoint 
disconnected etc).

Reproducer - add to ConnectionTest.java
{code:java}
    public void testServerDisconnect() {
        var server = new TestServer(0, new FakeIgnite(), null, null, "abc", 
clusterId, null, 10800);

        var client = IgniteClient.builder()
                .addresses("localhost")
                .build();

        client.tables().tables();

        server.close();

        client.tables().tables();
    }
{code}

  was:
In case of a server connection loss (node goes down, network issue, etc) the 
following warning appears in *client log*:

{code}
[2025-03-17T11:44:52,986][WARN ][nioEventLoopGroup-9-1][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.
 java.net.SocketException: Connection reset
        at 
java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:401)
 ~[?:?]
        at 
java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:434) ~[?:?]
        at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255) 
~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
        at 
io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) 
~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
        at io.netty.buffer.WrappedByteBuf.writeBytes(WrappedByteBuf.java:821) 
~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
        at 
io.netty.buffer.AdvancedLeakAwareByteBuf.writeBytes(AdvancedLeakAwareByteBuf.java:636)
 ~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
{code}

Improve exception handling and log a better warning (which endpoint 
disconnected etc).


> Java thin: weird warning on server disconnect
> ---------------------------------------------
>
>                 Key: IGNITE-24813
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24813
>             Project: Ignite
>          Issue Type: Bug
>          Components: thin client
>    Affects Versions: 3.0
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.1
>
>
> In case of a server connection loss (node goes down, network issue, etc) the 
> following warning appears in *client log*:
> {code}
> [2025-03-17T11:44:52,986][WARN 
> ][nioEventLoopGroup-9-1][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.
>  java.net.SocketException: Connection reset
>       at 
> java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:401)
>  ~[?:?]
>       at 
> java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:434) ~[?:?]
>       at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255) 
> ~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
>       at 
> io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) 
> ~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
>       at io.netty.buffer.WrappedByteBuf.writeBytes(WrappedByteBuf.java:821) 
> ~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
>       at 
> io.netty.buffer.AdvancedLeakAwareByteBuf.writeBytes(AdvancedLeakAwareByteBuf.java:636)
>  ~[netty-buffer-4.1.119.Final.jar:4.1.119.Final]
> {code}
> Improve exception handling and log a better warning (which endpoint 
> disconnected etc).
> Reproducer - add to ConnectionTest.java
> {code:java}
>     public void testServerDisconnect() {
>         var server = new TestServer(0, new FakeIgnite(), null, null, "abc", 
> clusterId, null, 10800);
>         var client = IgniteClient.builder()
>                 .addresses("localhost")
>                 .build();
>         client.tables().tables();
>         server.close();
>         client.tables().tables();
>     }
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to