[BACKPORT 4.2.x] Close connection on socket end as well as error (#1098) (#1108)

* Close connection on socket `end` as well as `error` (#1098)

* Fix links

Author: srknzl

DOCUMENTATION.md

@@ -494,7 +494,7 @@ That is because our map lives in the cluster and no matter which client we use,
 
 See the Hazelcast Node.js [code samples](https://github.com/hazelcast/hazelcast-nodejs-client/tree/master/code_samples) for more examples.
 
-You can also see the Hazelcast Node.js [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/api/current/docs/).
+You can also see the Hazelcast Node.js [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/).
 
 
 # 2. Features
@@ -589,7 +589,7 @@ Hazelcast serializes all your objects before sending them to the server. Certain
 
 > **NOTE: The `Long` type means the type provided by [long.js library](https://github.com/dcodeIO/long.js).**
 
-> **NOTE: A `number` is serialized as `Double` by default. You can configure this behavior using the `defaultNumberType` serialization config option. See [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/api/current/docs/) for more information.**
+> **NOTE: A `number` is serialized as `Double` by default. You can configure this behavior using the `defaultNumberType` serialization config option. See [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/) for more information.**
 
 Arrays of the `boolean`, `number`, `string`, and `Long` types can be serialized as `boolean[]`, `byte[]`, `short[]`, `int[]`, `float[]`, `double[]`, `string[]`, and `long[]` for the Java server side, respectively.
 
@@ -615,7 +615,7 @@ However, `JSON Serialization` may be not the best way of serialization in terms
 
 Or, if you want to use your own serialization method, you can use [Custom Serialization](#43-custom-serialization).
 
-> **NOTE: Hazelcast Node.js client is a TypeScript-based project but JavaScript does not have interfaces. Therefore, some interfaces are given to the user by using the TypeScript files that have `.ts` extension. In this guide, implementing an interface means creating an object to have the necessary functions that are listed in the interface inside the `.ts` file. Also, this object is mentioned as `an instance of the interface`. You can search the [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/api/current/docs/) or GitHub repository for a required interface.**
+> **NOTE: Hazelcast Node.js client is a TypeScript-based project but JavaScript does not have interfaces. Therefore, some interfaces are given to the user by using the TypeScript files that have `.ts` extension. In this guide, implementing an interface means creating an object to have the necessary functions that are listed in the interface inside the `.ts` file. Also, this object is mentioned as `an instance of the interface`. You can search the [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/) or GitHub repository for a required interface.**
 
 ## 4.1. IdentifiedDataSerializable Serialization
 
@@ -643,7 +643,7 @@ class Employee {
 }
 ```
 
-> **NOTE: Refer to `DataInput`/`DataOutput` interfaces in the [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/api/current/docs/) to understand methods available on the `input`/`output` objects.**
+> **NOTE: Refer to `DataInput`/`DataOutput` interfaces in the [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/) to understand methods available on the `input`/`output` objects.**
 
 The `IdentifiedDataSerializable` interface uses `classId` and `factoryId` properties to reconstitute the object. To complete the implementation, `IdentifiedDataSerializableFactory` factory function should also be implemented and put into the `serialization.dataSerializableFactories` config option. The factory's responsibility is to return an instance of the right `IdentifiedDataSerializable` object, given the `classId`.
 
@@ -713,7 +713,7 @@ class Customer {
 }
 ```
 
-> **NOTE: Refer to `PortableReader`/`PortableWriter` interfaces in the [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/api/current/docs/) to understand methods available on the `reader`/`writer` objects.**
+> **NOTE: Refer to `PortableReader`/`PortableWriter` interfaces in the [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/) to understand methods available on the `reader`/`writer` objects.**
 
 Similar to `IdentifiedDataSerializable`, a `Portable` object must provide `classId` and `factoryId`. The factory function will be used to create the `Portable` object given the `classId`.
 
@@ -1879,7 +1879,7 @@ Lifecycle Event >>> SHUTDOWN
 
 You can add event listeners to the distributed data structures.
 
-> **NOTE: Hazelcast Node.js client is a TypeScript-based project but JavaScript does not have interfaces. Therefore, some interfaces are given to the user by using the TypeScript files that have `.ts` extension. In this guide, implementing an interface means creating an object to have the necessary functions that are listed in the interface inside the `.ts` file. Also, this object is mentioned as "an instance of the interface". You can search the [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/api/current/docs/) or GitHub repository for the required interface.**
+> **NOTE: Hazelcast Node.js client is a TypeScript-based project but JavaScript does not have interfaces. Therefore, some interfaces are given to the user by using the TypeScript files that have `.ts` extension. In this guide, implementing an interface means creating an object to have the necessary functions that are listed in the interface inside the `.ts` file. Also, this object is mentioned as "an instance of the interface". You can search the [API Documentation](http://hazelcast.github.io/hazelcast-nodejs-client/) or GitHub repository for the required interface.**
 
 #### 8.5.2.1. Map Listener
 

README.md

@@ -125,7 +125,7 @@ You can use the following channels for your questions and development/usage issu
 
 * [GitHub repository](https://github.com/hazelcast/hazelcast-nodejs-client)
 * [Complete documentation](DOCUMENTATION.md)
-* [API documentation](http://hazelcast.github.io/hazelcast-nodejs-client/api/current/docs/)
+* [API documentation](http://hazelcast.github.io/hazelcast-nodejs-client/)
 * [Slack](https://slack.hazelcast.com)
 * [Google Groups](https://groups.google.com/forum/#!forum/hazelcast)
 * [Stack Overflow](https://stackoverflow.com/questions/tagged/hazelcast)

src/network/ConnectionManager.ts

@@ -458,7 +458,12 @@ export class ConnectionManager extends EventEmitter {
                 );
                 // close the connection proactively on errors
                 socket.once('error', (err: NodeJS.ErrnoException) => {
-                    connection.close('Socket error. Connection might be closed by other side', err);
+                    connection.close('Socket error.', err);
+                });
+                // close the connection if socket is not readable anymore
+                socket.once('end', () => {
+                    const reason = 'Connection closed by the other side.';
+                    connection.close(reason, new IOError(reason));
                 });
                 return this.initiateCommunication(socket);
             })