Package com.couchbase.client.core.cnc.events.io
package com.couchbase.client.core.cnc.events.io
-
ClassDescriptionThis warning indicates that the client closed an active IO channel/socket proactively because it detected an invalid state.Specifies the reasons why a channel has been proactively closed by the SDK.This event is emitted if the user has configured a custom list of tls ciphers.This event is raised if a durability timeout has been provided out of the allowed range and is coerced into a sane and supported value.The KV error map got negotiated loaded from the server.If loading the KV error map for some reason fails, this event will capture the KV status code.If the KV error map could be loaded, but the decoding of the buffer from JSON failed, this event will be raised.Captures the end of the KV feature negotiation.Raised when a http config streaming connection is closed because of the configured configIdleRedialTimeout.This event is created if somewhere in the IO layer an invalid packet was detected.If this event is raised, it indicates a serious bug in the system.Raised if an unknown error is decoded and handled through the KV error map.This event is raised if a KV response with "not my vbucket" is received.If something goes wrong during the SASL authentication process, this event is raised.This event is raised if we need to re-do the SASL auth for a connection because the mechanisms did not match up with the best-effort first try.This debug event signals that SASL auth mechanisms have been listed from the server.This debug event signals that a SASL auth mechanism has been negotiated between the client and the server.This event gets created as soon as a bucket has been selected during the KV bootstrap process for each socket/node.If selecting a bucket during KV bootstrap fails, this is a really problematic issue and needs to be looked at.This event is raised if the client detects an unknown SASL mechanism it cannot turn into an enum.If the server sends us unsolicited features during the HELLO negotiation, this event will be raised - it is a warning severity since it indicates a server bug.