[
https://issues.apache.org/jira/browse/KUDU-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133840#comment-16133840
]
Todd Lipcon commented on KUDU-1894:
-----------------------------------
Deadlock cycle seems to be:
- Thread-9:
-- holds Connection.lock
-- trying to acquire SslHandler.handshakeLock in SslHandler.wrap
- Netty worker:
-- SslHandler calling handleRenegotiation holding handshakeLock ends up firing
channelDisconnected, which eventually triggers Connection.cleanup, which wants
to take Connection.lock
> ITClient very flaky since introduction of TLS
> ---------------------------------------------
>
> Key: KUDU-1894
> URL: https://issues.apache.org/jira/browse/KUDU-1894
> Project: Kudu
> Issue Type: Bug
> Components: java
> Affects Versions: 1.3.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Fix For: n/a
>
>
> Since introducing TLS support in the Java client, ITClient seems to
> hang/timeout quite often. It always spews some error about TLS renegotiation,
> but it seems like that error description is incorrect -- really it seems more
> likely that something is amiss with the way this test tries to shut down
> client connections by reaching into the Netty channel.
> Either way we should investigate for 1.3.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
