Use simplified toString() implementation to avoid possible deadlocks - #688
Open
turbanoff wants to merge 1 commit into
Open
Use simplified toString() implementation to avoid possible deadlocks#688turbanoff wants to merge 1 commit into
turbanoff wants to merge 1 commit into
Conversation
ok2c
approved these changes
Aug 13, 2026
ok2c
left a comment
Member
There was a problem hiding this comment.
@turbanoff Looks good to me. I have to say though #toString method should never get executed in normal circumstances in the productive mode, unless one explicitly turns on i/o session debug logging
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We got a deadlock in one of our applications
As you can see essential part of deadlock is
SSLIOSession.toString()method which atempts to acuire the lock.As a fix I propose to use
tryLockinstead and show only id+status when tryLock failed.idis final in the main IOSession implementation - IOSessionImpl (shouldn't lead to any concurrency problems)statusis volatile enum field, so can be accessed without synchronization.