We're updating the issue view to help you get more done. 

Exception thrown during socket reading should not leave the component connection in a weird state

Description

Justin Karneges reports this bug via e-mail:

We encountered an issue where Whack's socket read thread will end, but no component reconnection is made. The connection is still open, just not being
read from anymore. (...) Make sure that any exception thrown during socket reading does not leave the component connection in a weird state. Either the error is non-fatal, and everything should continue normally, or the error is fatal, the socket should be disconnected and reconnected as normal.

Environment

None

Acceptance Test - Entry

None

Assignee

Guus der Kinderen

Reporter

Guus der Kinderen

Labels

None

Expected Effort

None

Ignite Forum URL

None

Components

Priority

Major
Configure