Reason
Why the exchange failed.
This set may gain constants in any minor release, also after 1.0, as kcoap covers more transports and more of the RFCs (DTLS, for one): a when over a reason keeps an else branch, which then handles a reason it does not know, such as by treating it as a failure of the peer. A new constant is an addition, not a breaking change (the project's versioning policy, docs/versioning.md).
Entries
A Confirmable message was not acknowledged within MAX_TRANSMIT_WAIT (RFC 7252 §4.2). Datagrams only: a connection has no acknowledgements (RFC 8323 §3.1), and its loss is CONNECTION_CLOSED.
No response arrived in time after the request was sent or acknowledged.
The secure session to the peer ended: its DTLS session over datagrams, which RFC 7252 §9.1.1 forbids retransmitting across. A connection that ends is CONNECTION_CLOSED.
The endpoint's own transport failed, not the peer: its datagram transport stopped receiving, which closes the endpoint for good, or refused to carry a message to the peer at all, which no retransmission can fix. The cause is the transport's exception.
The endpoint has no transport for the peer, so nothing was sent: a coap or coaps peer of an endpoint without a datagram transport, or a peer of an RFC 8323 scheme that no connector serves and that has no connection open. The message names the scheme. A configuration mistake rather than a failure of the peer: the endpoint needs that transport.
A response violated the protocol, for example an unrecognized critical option (RFC 7252 §5.4.1).
A block-wise transfer could not be completed (RFC 7959), for example blocks of changing ETags.
A message is larger than the transport or the peer allows: the datagram size, or the peer's Max-Message-Size on a connection (RFC 8323 §5.3.1).
All Message IDs or tokens for a peer are in use (RFC 7252 §4.4, §5.3.1).
The connection to the peer (RFC 8323) could not be opened, or it closed, was released or aborted before the exchange completed. The message says which; RFC 8323 §3.4 leaves reconnecting to the application.
A request protected by message security got, before any verified response, a response the security layer could not verify: an error without message security, such as OSCORE's unprotected 4.01 or 4.02 (RFC 8613 §8.2), which anyone who saw the token can send (CoapException.response holds it). The client acted on nothing in it: it did not repeat the request with an Echo value, continue a body or change what it knows about the server (ADR 0008). The request may have been processed or not, so repeating a request that is not idempotent may run it twice; a server that lost its security context answers this way too, and running the key establishment again, such as EDHOC, is the usual remedy.
Message security on this side failed, so nothing was sent: the client's ClientMessageSecurity could not protect the request. The cause is the security layer's exception, such as kcoap-oscore's MessageSecurityException for a peer without a security context, exhausted sequence numbers (RFC 8613 §7.2.1) or a sequence-number store that failed. A configuration or key-management matter rather than a failure of the peer: retrying succeeds only once the context is fixed, for example by running EDHOC.
The host of the request's URI could not be resolved, so nothing was sent: the client's EndpointResolver failed at runtime, as a DNS lookup does without network or for a name without an address. The cause is the resolver's exception, if any. A condition that may pass, unlike a resolver that cannot resolve such a host at all, which is a mistake of configuration and throws IllegalArgumentException.
Properties
Functions
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
Returns an array containing the constants of this enum type, in the order they're declared.