You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2021/04/16 13:40:00 UTC

[jira] [Comment Edited] (QPIDJMS-535) Looping failure after SASL negotiation with Artemis v2.16

    [ https://issues.apache.org/jira/browse/QPIDJMS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323822#comment-17323822 ] 

Robbie Gemmell edited comment on QPIDJMS-535 at 4/16/21, 1:39 PM:
------------------------------------------------------------------

The connection is being closed/refused by the broker due to the broker saying the connection has failed, due to the container-id already being in use by an existing connection. Either it is, or is being mistakenly considered so by the broker. Its certainly not a client bug. I recall a similar issue being raised for Artemis previously.


was (Author: gemmellr):
The connection is being closed/refused by the broker to the broker saying the connection has failed, due to the container-id already being in use by an existing connection. Either it is, or is being mistakenly considered so by the broker. Its certainly not a client bug. I recall a similar issue being raised for Artemis previously.

> Looping failure after SASL negotiation with Artemis v2.16
> ---------------------------------------------------------
>
>                 Key: QPIDJMS-535
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-535
>             Project: Qpid JMS
>          Issue Type: Bug
>    Affects Versions: 0.58.0
>            Reporter: David Martin
>            Priority: Minor
>
> This is not a production issue for us so tagging it as minor. Encountered during some destructive testing, killing brokers, clients, seeing that connections re-establish ok.
> It sometimes happens when re-establishing a connection to an artemis broker hosted in kubernetes which has been recycled by deleting the pod.
> {noformat}
> 2021-04-09 11:48:13.940 DEBUG 11152 --- [.84.10.4:30672]] proton.trace                             : IN: CH[28] : Flow{nextIncomingId=1, incomingWindow=2147483647, nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=14000, linkCredit=0, available=null, drain=true, echo=false, properties=null}
> 2021-04-09 11:48:14.278  INFO 11152 --- [.84.10.4:30672]] o.a.qpid.jms.provider.amqp.AmqpProvider  : Transport failed: An existing connection was forcibly closed by the remote host
> 2021-04-09 11:48:14.324 DEBUG 11152 --- [.84.10.4:30672]] io.netty.buffer.PoolThreadCache          : Freed 18 thread-local buffer(s) from thread: AmqpProvider :(1):[amqp://10.84.10.4:30672]
> 2021-04-09 11:48:36.778 DEBUG 11152 --- [.84.10.4:30672]] o.a.qpid.jms.sasl.SaslMechanismFinder    : Best match for SASL auth was: SASL-PLAIN
> 2021-04-09 11:48:36.862 DEBUG 11152 --- [.84.10.4:30672]] o.a.qpid.proton.engine.impl.SaslImpl     : Handled outcome: SaslImpl [_outcome=PN_SASL_OK, state=PN_SASL_PASS, done=true, role=CLIENT]
> 2021-04-09 11:48:36.936 DEBUG 11152 --- [.84.10.4:30672]] proton.trace                             : IN: CH[0] : Open{ containerId='', hostname='null', maxFrameSize=131072, channelMax=65535, idleTimeOut=null, outgoingLocales=null, incomingLocales=null, offeredCapabilities=null, desiredCapabilities=null, properties={amqp:connection-establishment-failed=true}}
> 2021-04-09 11:48:36.937 DEBUG 11152 --- [.84.10.4:30672]] proton.trace                             : IN: CH[0] : Close{error=Error{condition=amqp:invalid-field, description='null', info={invalid-field=container-id}}}
> 2021-04-09 11:48:36.940 DEBUG 11152 --- [.84.10.4:30672]] io.netty.buffer.PoolThreadCache          : Freed 3 thread-local buffer(s) from thread: AmqpProvider :(3):[amqp://10.84.10.4:30672]
> 2021-04-09 11:48:37.128 DEBUG 11152 --- [.84.10.4:30672]] o.a.qpid.jms.sasl.SaslMechanismFinder    : Best match for SASL auth was: SASL-PLAIN
> 2021-04-09 11:48:37.200 DEBUG 11152 --- [.84.10.4:30672]] o.a.qpid.proton.engine.impl.SaslImpl     : Handled outcome: SaslImpl [_outcome=PN_SASL_OK, state=PN_SASL_PASS, done=true, role=CLIENT]
> 2021-04-09 11:48:37.274 DEBUG 11152 --- [.84.10.4:30672]] proton.trace                             : IN: CH[0] : Open{ containerId='', hostname='null', maxFrameSize=131072, channelMax=65535, idleTimeOut=null, outgoingLocales=null, incomingLocales=null, offeredCapabilities=null, desiredCapabilities=null, properties={amqp:connection-establishment-failed=true}}
> 2021-04-09 11:48:37.274 DEBUG 11152 --- [.84.10.4:30672]] proton.trace                             : IN: CH[0] : Close{error=Error{condition=amqp:invalid-field, description='null', info={invalid-field=container-id}}}
> 2021-04-09 11:48:37.276 DEBUG 11152 --- [.84.10.4:30672]] io.netty.buffer.PoolThreadCache          : Freed 3 thread-local buffer(s) from thread: AmqpProvider :(4):[amqp://10.84.10.4:30672]
> 2021-04-09 11:48:37.486 DEBUG 11152 --- [.84.10.4:30672]] o.a.qpid.jms.sasl.SaslMechanismFinder    : Best match for SASL auth was: SASL-PLAIN
> 2021-04-09 11:48:37.557 DEBUG 11152 --- [.84.10.4:30672]] o.a.qpid.proton.engine.impl.SaslImpl     : Handled outcome: SaslImpl [_outcome=PN_SASL_OK, state=PN_SASL_PASS, done=true, role=CLIENT]
> 2021-04-09 11:48:37.629 DEBUG 11152 --- [.84.10.4:30672]] proton.trace                             : IN: CH[0] : Open{ containerId='', hostname='null', maxFrameSize=131072, channelMax=65535, idleTimeOut=null, outgoingLocales=null, incomingLocales=null, offeredCapabilities=null, desiredCapabilities=null, properties={amqp:connection-establishment-failed=true}}
> 2021-04-09 11:48:37.629 DEBUG 11152 --- [.84.10.4:30672]] proton.trace                             : IN: CH[0] : Close{error=Error{condition=amqp:invalid-field, description='null', info={invalid-field=container-id}}}
> 2021-04-09 11:48:37.631 DEBUG 11152 --- [.84.10.4:30672]] io.netty.buffer.PoolThreadCache          : Freed 3 thread-local buffer(s) from thread: AmqpProvider :(5):[amqp://10.84.10.4:30672]
> 2021-04-09 11:48:37.875 DEBUG 11152 --- [.84.10.4:30672]] o.a.qpid.jms.sasl.SaslMechanismFinder    : Best match for SASL auth was: SASL-PLAIN
> 2021-04-09 11:48:37.945 DEBUG 11152 --- [.84.10.4:30672]] o.a.qpid.proton.engine.impl.SaslImpl     : Handled outcome: SaslImpl [_outcome=PN_SASL_OK, state=PN_SASL_PASS, done=true, role=CLIENT]
> 2021-04-09 11:48:38.015 DEBUG 11152 --- [.84.10.4:30672]] proton.trace                             : IN: CH[0] : Open{ containerId='', hostname='null', maxFrameSize=131072, channelMax=65535, idleTimeOut=null, outgoingLocales=null, incomingLocales=null, offeredCapabilities=null, desiredCapabilities=null, properties={amqp:connection-establishment-failed=true}}
> 2021
>  {noformat}
> ... and so on. Only restarting the client makes it reconnect. The connection is non-SSL AMQP from a client in a pod to a broker in a pod. Using a Spring CachingConnectionFactory with resetConnectionOnException enabled. In production will go via an external load balancer with SSL and not seeing the same problem there.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org