This repository was archived by the owner on Jul 1, 2022. It is now read-only.
Fix repeatedly error logging for HttpSender (#732) #785
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.
Which problem is this PR solving?
HttpSenderis usedUdpSenderis used (see description)Short description of the changes
Resolves #732 - repeatedly error logging when
HttpSenderis used. The problem was that removing "failed" command fromcommandFailedBeforeHashSet was always done when command execution ends successfully (i.e. without throwingSenderException). But there are some situations, when "span is only saved in a buffer" on sender level (or there is no any span to be sent) and remote communication is not started at all.Unfortunately the solution does not solve a problem if
UdpSenderis used. The reason is thatPortUnreachableExceptionis not thrown immediately, whenDatagramSocket.send(DatagramPacket)method is invoked - this exception is thrown when subsequent call to send or receive is done. See Javadoc: