[
https://issues.apache.org/jira/browse/PROTON-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798945#comment-16798945
]
Daniel Maier commented on PROTON-1996:
--------------------------------------
I can confirm configuring initialHandshakeTimeoutSeconds avoids this issue.
Also we created an overall connection timeout with connection retry in our
client, which is eclipse hono client:
https://github.com/eclipse/hono/issues/1022.
However we never found the root cause of this. As it works now for us, we would
be fine to close this issue if nobody else has an idea for the root cause.
I never mentioned this: we use
https://github.com/EnMasseProject/enmasse/tree/master/keycloak-plugin for SASL
authentication if this is important for this issue.
> Proton Client is "stalled" during SASL handshake
> ------------------------------------------------
>
> Key: PROTON-1996
> URL: https://issues.apache.org/jira/browse/PROTON-1996
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: proton-j-0.25.0, proton-j-0.31.0
> Reporter: Daniel Maier
> Priority: Major
>
> Hi,
> When I try to connect with proton vertx client to an AMQP server, the client
> seems to come sporadically in some kind of "stalled" state. The logs, see
> below, look like the server just not responds anymore which cause the client
> to be stalled. There are no more logs regarding SASL handshake.
> Used server is qdrouter.
> Would it make sense from your point of view to introduce a timeout here? Or
> is the responsibility for this in the calling application?
> {code}
> 08:32:49.412 [vert.x-eventloop-thread-0] DEBUG
> o.a.qpid.proton.engine.impl.SaslImpl - Finished writing SASL output. Output
> Buffer : java.nio.HeapByteBuffer[pos=8 lim=512 cap=512]
> 08:32:49.412 [vert.x-eventloop-thread-0] DEBUG
> o.a.qpid.proton.engine.impl.SaslImpl - Finished writing SASL output. Output
> Buffer : java.nio.HeapByteBuffer[pos=8 lim=512 cap=512]
> 08:32:49.412 [vert.x-eventloop-thread-0] DEBUG
> o.a.qpid.proton.engine.impl.SaslImpl - Finished writing SASL output. Output
> Buffer : java.nio.HeapByteBuffer[pos=8 lim=512 cap=512]
> 08:32:49.412 [vert.x-eventloop-thread-0] DEBUG
> o.a.qpid.proton.engine.impl.SaslImpl - Finished writing SASL output. Output
> Buffer : java.nio.HeapByteBuffer[pos=0 lim=512 cap=512]
> 08:32:49.412 [vert.x-eventloop-thread-0] DEBUG
> o.a.qpid.proton.engine.impl.SaslImpl - Finished writing SASL output. Output
> Buffer : java.nio.HeapByteBuffer[pos=0 lim=512 cap=512]
> 08:32:49.412 [vert.x-eventloop-thread-0] DEBUG
> o.a.qpid.proton.engine.impl.SaslImpl - Finished writing SASL output. Output
> Buffer : java.nio.HeapByteBuffer[pos=0 lim=512 cap=512]
> 08:32:49.412 [vert.x-eventloop-thread-0] DEBUG
> io.netty.handler.ssl.SslHandler - [id: 0x429f2c43, L:/100.100.0.6:45982 -
> R:xxx.com/xxx:443] HANDSHAKEN: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> 08:32:49.418 [vert.x-eventloop-thread-0] DEBUG
> o.a.qpid.proton.engine.impl.SaslImpl - SaslImpl [_outcome=PN_SASL_NONE,
> state=PN_SASL_IDLE, done=false, role=CLIENT] about to call input.
> 08:32:49.418 [vert.x-eventloop-thread-0] TRACE
> io.vertx.proton.impl.ProtonTransport - New Proton Event: CONNECTION_INIT
> 08:32:49.418 [vert.x-eventloop-thread-0] DEBUG
> o.a.qpid.proton.engine.impl.SaslImpl - Finished writing SASL output. Output
> Buffer : java.nio.HeapByteBuffer[pos=0 lim=512 cap=512]
> 08:32:49.418 [vert.x-eventloop-thread-0] DEBUG
> o.a.qpid.proton.engine.impl.SaslImpl - Finished writing SASL output. Output
> Buffer : java.nio.HeapByteBuffer[pos=0 lim=512 cap=512]
> {code}
> Thanks
> Daniel
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
