Server unresponsive after cancelled socket #2

Closed
opened 2020-02-08 10:39:20 +01:00 by CyB3RC0nN0R · 1 comment
CyB3RC0nN0R commented 2020-02-08 10:39:20 +01:00 (Migrated from github.com)

Describe the bug
When a client disconnects unexpectedly and the Socket is therefore cancelled, the server does not properly respond to incoming objects.

To Reproduce
Steps to reproduce the behavior:

  1. Start a client and connect to the server
  2. Terminate the client
  3. Try to connect a second time

Expected behavior
The server operation should continue as intended.

Additional context
The fix will probably depend on java-nio-server.

**Describe the bug** When a client disconnects unexpectedly and the `Socket` is therefore cancelled, the server does not properly respond to incoming objects. **To Reproduce** Steps to reproduce the behavior: 1. Start a client and connect to the server 2. Terminate the client 3. Try to connect a second time **Expected behavior** The server operation should continue as intended. **Additional context** The fix will probably depend on `java-nio-server`.
CyB3RC0nN0R commented 2020-02-09 14:40:36 +01:00 (Migrated from github.com)

The IOException is thrown in ObjectMessageReader due to the socket not being able to read into the message buffer. This exception is then catched inside the server loop defined inside java-nio-server, which is then left. Therefore no further messages can be read.

The `IOException` is thrown in `ObjectMessageReader` due to the socket not being able to read into the message buffer. This exception is then catched inside the server loop defined inside `java-nio-server`, which is then left. Therefore no further messages can be read.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: zdm/java-nio-server#2
No description provided.