Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StacklessSSLHandshakeException: add a short stack-trace #13315

Merged

Conversation

idelpivnitskiy
Copy link
Member

Motivation:

Currently, StacklessSSLHandshakeException doesn't have any stack-trace which makes it harder to understand where it comes from.

Modifications:

  • Add one-line stack-trace using ThrowableUtil.unknownStackTrace utility;

Result:

Similar to StacklessClosedChannelException,
StacklessSSLHandshakeException always has one-line stack-trace to indicate where it originated.

Motivation:

Currently, `StacklessSSLHandshakeException` doesn't have any stack-trace
which makes it harder to understand where it comes from.

Modifications:

- Add one-line stack-trace using `ThrowableUtil.unknownStackTrace`
utility;

Result:

Similar to `StacklessClosedChannelException`,
`StacklessSSLHandshakeException` always has one-line stack-trace to
indicate where it was originated.
@idelpivnitskiy
Copy link
Member Author

cc @hyperxpro

Copy link
Contributor

@hyperxpro hyperxpro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks clean! :)

@normanmaurer normanmaurer merged commit e1fad99 into netty:4.1 Apr 1, 2023
9 of 14 checks passed
@normanmaurer normanmaurer added this to the 4.1.91.Final milestone Apr 1, 2023
@idelpivnitskiy idelpivnitskiy deleted the StacklessSSLHandshakeException branch April 1, 2023 15:30
idelpivnitskiy added a commit to idelpivnitskiy/netty that referenced this pull request Apr 1, 2023
Motivation:

Currently, `StacklessSSLHandshakeException` doesn't have any stack-trace
which makes it harder to understand where it comes from.

Modifications:

- Add one-line stack-trace using `ThrowableUtil.unknownStackTrace`
utility;

Result:

Similar to `StacklessClosedChannelException`,
`StacklessSSLHandshakeException` always has one-line stack-trace to
indicate where it was originated.
normanmaurer pushed a commit that referenced this pull request Apr 2, 2023
…13316)

Motivation:

Currently, `StacklessSSLHandshakeException` doesn't have any stack-trace
which makes it harder to understand where it comes from.

Modifications:

- Add one-line stack-trace using `ThrowableUtil.unknownStackTrace`
utility;

Result:

Similar to `StacklessClosedChannelException`,
`StacklessSSLHandshakeException` always has one-line stack-trace to
indicate where it was originated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants