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?
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?
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]
I also created this issue in proton-j project: https://issues.apache.org/jira/browse/PROTON-1996. But it turned out it would make more sense to discuss some sort of timeout here.
Thanks Daniel