Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server warning on clean disconnection of client (hazelcast-client-new) #6035

Closed
em-chips opened this issue Aug 21, 2015 · 3 comments

Comments

Projects
None yet
5 participants
@em-chips
Copy link

commented Aug 21, 2015

When the client disconnects normally, the server logs an info and a warning message containing the text java.io.EOFException. This occurs on HC 3.5.1 at least.

Eg.

Aug 21, 2015 2:05:13 PM com.hazelcast.nio.tcp.TcpIpConnection
INFO: [127.0.0.1]:5701 [dev] [3.5.1] Connection [Address[127.0.0.1]:50771] lost. Reason: java.io.EOFException[Remote socket closed!]
Aug 21, 2015 2:05:13 PM com.hazelcast.nio.tcp.ReadHandler
WARNING: [127.0.0.1]:5701 [dev] [3.5.1] hz._hzInstance_1_dev.IO.thread-in-0 Closing socket to endpoint Address[127.0.0.1]:50771, Cause:java.io.EOFException: Remote socket closed!

Many log monitoring systems will be set up to trigger alerts on the presence of exception messages or warnings in the server logs. So here an ordered disconnection will trigger a false alarm.

Reproduce with

    public static void main(String[] args) {
        HazelcastInstance server = Hazelcast.newHazelcastInstance(new Config());
        HazelcastInstance client = HazelcastClient.newHazelcastClient(new ClientConfig());
        client.shutdown();
        server.shutdown();
    }
@em-chips

This comment has been minimized.

Copy link
Author

commented Aug 28, 2015

It does the same on 3.5.2

@enesakar enesakar removed the PENDING label Nov 2, 2015

@sancar sancar added this to the 3.7 milestone Nov 20, 2015

@pveentjer pveentjer self-assigned this May 3, 2016

@pveentjer

This comment has been minimized.

Copy link
Member

commented May 3, 2016

Thanks for reporting. I'll fix this one.

@anilkumardesai

This comment has been minimized.

Copy link

commented Jan 11, 2017

We are using 3.6.2 and still seeing these in our logs. Is this issue closed?

01/11/2017 14:14:38,465 - INFO [hz._hzInstance_1_FB_API.IO.thread-in-0][][com.hazelcast.nio.tcp.TcpIpConnection] [127.0.0.1]:31201 [FB_API] [3.6.2] Connection [Address[127.0.0.1]:59972] lost. Reason: java.io.EOFException[Remote socket closed!]
01/11/2017 14:14:38,466 - WARN [hz._hzInstance_1_FB_API.IO.thread-in-0][][com.hazelcast.nio.tcp.nonblocking.NonBlockingSocketReader] [127.0.0.1]:31201 [FB_API] [3.6.2] hz._hzInstance_1_FB_API.IO.thread-in-0 Closing socket to endpoint Address[127.0.0.1]:59972, Cause:java.io.EOFException: Remote socket closed!
01/11/2017 14:14:38,467 - INFO [hz._hzInstance_1_FB_API.event-3][][com.hazelcast.client.ClientEndpointManager] [127.0.0.1]:31201 [FB_API] [3.6.2] Destroying ClientEndpoint{conn=Connection [0.0.0.0/0.0.0.0:31201 -> /127.0.0.1:59972], endpoint=Address[127.0.0.1]:59972, alive=false, type=JAVA_CLIENT, principal='ClientPrincipal{uuid='7181902f-8fe9-4065-b610-5a0e9c4ad212', ownerUuid='7ff02f81-c0e3-4094-a968-507c7df4df9f'}', firstConnection=true, authenticated=true}
01/11/2017 14:14:38,467 - INFO [hz._hzInstance_1_FB_API.event-3][][com.hazelcast.transaction.TransactionManagerService] [127.0.0.1]:31201 [FB_API] [3.6.2] Committing/rolling-back alive transactions of client, UUID: 7181902f-8fe9-4065-b610-5a0e9c4ad212
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.