tree 475f8a3b4d43dbe39d579da357fad67f92c99a53
parent 98dd7f6260ab1537614d44cab794b921656c167d
author Murtadha Hubail <mhubail@apache.org> 1534200253 -0700
committer Murtadha Hubail <mhubail@apache.org> 1534206578 -0700

[NO ISSUE][NET] Skip Channel Write on Connection Failure

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
- Do not attempt to adjust channel writability if
  the failure was due to connection failure since
  no more messages will be sent on that connection.
  This is done to prevent a possible deadlock between
  network IOThread that detected connection failure
  and another thread that might be accessing the channel.
- Make sending error code conditions more explicit since
  we currently have a single error code that is sent.

Change-Id: Ic25f05ac2c0d02699324f2d1b80c51f392654106
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2892
Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Michael Blow <mblow@apache.org>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>