Fixed problems in handshake handling #361
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes:
startConnect
was catching a not possible behavior. The condition stayed, but it is turned into just an IPE error message.CONN_REJECT
and was not properly handled - this adds the exception inforemoveConnector
previously applied when the process gets broken due to rejection. Instead the removal is done only in case when this function is about to finish and throw exception due to any case of abnormal result.processRendezvous
the "response" packet is checked if it contains data (otherwise payload size is set to -1). There were cases when a non-received payload packet was passed to this function and was interpreted as infinite-size content causing a crashupdateConnStatus
respond anything only in asynchronous mode (this was probably allowed in synchronous mode in UDT because it was an accidental patch to a bug). Keeping this running in synchronous mode might in specific cases cause processing the incoming packet in two FAs and two threads separately in areas that weren't predicted to be protected against simultaneous access