Connection to
become available.Connection to
become available.Connection to the pool.Connection to the pool.MultiEndpointPool.SingleEndpointPool.SingleEndpointPool.Builder.SingleEndpointPool.Builder.IOException if the pool has been closed.Connection information, that might be used for monitoring reasons.Connection could be associated
with the pool.Connection could be associated
with the pool.Connection could stay registered with the pool
Once timeout is hit - the connection will be either closed, if it's idle,
or detached from the pool, if it's being used.Endpoint must always know how to establish the connectionConnectorHandler used to establish new ConnectionsConnectorHandler used to establish new Connections.Connection connect operation may take.Connection connect operation may take.Connections, kept in the pool, that are immune to keep-alive mechanismConnections, kept in the pool,
that are immune to keep-alive mechanism.Connection by calling
SingleEndpointPool.checkBeforeOpeningConnection() and if it is possible - establish
new connection.SingleEndpointPool instance.DelayedExecutor to be used for keep-alive and
reconnect mechanismsDelayedExecutor to be used for keep-alive and
reconnect mechanisms.DelayedExecutor to be used for keep-alive and
reconnect mechanisms.Connection from the pool.Connection from the pool.Connection to the endpoint.ConnectorHandler and endpoint address.Endpoint implementation.ConnectorHandler.ConnectionInfo, that might be used for monitoring
reasons, or null if the Connection does not belong to
this pool.ConnectionInfo, that might be used for monitoring
reasons, or null if the Connection does not belong to
this pool.Connection could be associated with the pool.Connection could be associated with the pool.Connection will be kept
in the pool.Connection will be kept
in the pool.Connection is registered in
the pool and is currently in busy state (used by a user), otherwise
returns false.Connection is registered in
the pool and is currently in busy state (used by a user), otherwise
returns false.Connection is registered in the pool
no matter if it's currently in busy or ready state, or false if
the Connection is not registered in the pool.Connection is registered in the pool
no matter if it's currently in busy or ready state, or false if
the Connection is not registered in the pool.Connections check.Connections check.Connections checkConnection
will be kept in the pool.Connection
will be kept in the pool.Connection will be
kept in the pool.Chain is built.Connections to a single endpoint
the pool is allowed to have.Connections the pool is allowed to have.Connections kept by this poolConnections kept by this pool.Connections kept by this poolConnection pool implementation where each endpoint
sub-pool is represented by SingleEndpointPool and referenced by an Endpoint.SingleEndpointPool.SingleEndpointPool associated with the specific endpoint
represented by Endpoint.Connection related to the
Endpoint is established.Connection to the pool.Connection to the pool.Connection pool implementation, in other words
this pool manages Connections to one specific endpoint.SingleEndpointPool.Connection to the specified endpoint from the pool in
non-blocking/asynchronous fashion.Connection to the specified endpoint from the pool
in non-blocking/asynchronous fashion.Connection from the pool in non-blocking/asynchronous fashion.Connection from the pool in non-blocking/asynchronous fashion.Copyright © 2020 Oracle Corporation. All Rights Reserved.