Class AbstractConnector
- All Implemented Interfaces:
Connector
,Container
,Destroyable
,Dumpable
,Dumpable.DumpableContainer
,Graceful
,LifeCycle
- Direct Known Subclasses:
AbstractNetworkConnector
,LocalConnector
,UnixSocketConnector
An abstract implementation of Connector
that provides a ConnectionFactory
mechanism
for creating Connection
instances for various protocols (HTTP, SSL, etc).
Connector Services
The abstract connector manages the dependent services needed by all specific connector instances:- The
Executor
service is used to run all active tasks needed by this connector such as accepting connections or handle HTTP requests. The default is to use theServer.getThreadPool()
as an executor. - The
Scheduler
service is used to monitor the idle timeouts of all connections and is also made available to the connections to time such things as asynchronous request timeouts. The default is to use a newScheduledExecutorScheduler
instance. - The
ByteBufferPool
service is made available to all connections to be used to acquire and releaseByteBuffer
instances from a pool. The default is to use a newArrayByteBufferPool
instance.
ContainerLifeCycle
super class and
may either be managed or unmanaged beans.
Connection Factories
The connector keeps a collection ofConnectionFactory
instances, each of which are known by their
protocol name. The protocol name may be a real protocol (e.g. "http/1.1" or "h2") or it may be a private name
that represents a special connection factory. For example, the name "SSL-http/1.1" is used for
an SslConnectionFactory
that has been instantiated with the HttpConnectionFactory
as it's
next protocol.
Configuring Connection Factories
The collection of availableConnectionFactory
may be constructor injected or modified with the
methods addConnectionFactory(ConnectionFactory)
, removeConnectionFactory(String)
and
setConnectionFactories(Collection)
. Only a single ConnectionFactory
instance may be configured
per protocol name, so if two factories with the same ConnectionFactory.getProtocol()
are set, then
the second will replace the first.
The protocol factory used for newly accepted connections is specified by
the method setDefaultProtocol(String)
or defaults to the protocol of the first configured factory.
Each Connection factory type is responsible for the configuration of the protocols that it accepts. Thus to
configure the HTTP protocol, you pass a HttpConfiguration
instance to the HttpConnectionFactory
(or other factories that can also provide HTTP Semantics). Similarly the SslConnectionFactory
is
configured by passing it a SslContextFactory
and a next protocol name.
Connection Factory Operation
ConnectionFactory
s may simply create a Connection
instance to support a specific
protocol. For example, the HttpConnectionFactory
will create a HttpConnection
instance
that can handle http/1.1, http/1.0 and http/0.9.
ConnectionFactory
s may also create a chain of Connection
instances, using other ConnectionFactory
instances.
For example, the SslConnectionFactory
is configured with a next protocol name, so that once it has accepted
a connection and created an SslConnection
, it then used the next ConnectionFactory
from the
connector using the getConnectionFactory(String)
method, to create a Connection
instance that
will handle the unencrypted bytes from the SslConnection
. If the next protocol is "http/1.1", then the
SslConnectionFactory
will have a protocol name of "SSL-http/1.1" and lookup "http/1.1" for the protocol
to run over the SSL connection.
ConnectionFactory
s may also create temporary Connection
instances that will exchange bytes
over the connection to determine what is the next protocol to use. For example the ALPN protocol is an extension
of SSL to allow a protocol to be specified during the SSL handshake. ALPN is used by the HTTP/2 protocol to
negotiate the protocol that the client and server will speak. Thus to accept an HTTP/2 connection, the
connector will be configured with ConnectionFactory
s for "SSL-ALPN", "h2", "http/1.1"
with the default protocol being "SSL-ALPN". Thus a newly accepted connection uses "SSL-ALPN", which specifies a
SSLConnectionFactory with "ALPN" as the next protocol. Thus an SSL connection instance is created chained to an ALPN
connection instance. The ALPN connection then negotiates with the client to determined the next protocol, which
could be "h2" or the default of "http/1.1". Once the next protocol is determined, the ALPN connection
calls getConnectionFactory(String)
to create a connection instance that will replace the ALPN connection as
the connection chained to the SSL connection.
Acceptors
The connector will execute a number of acceptor tasks to theException
service passed to the constructor.
The acceptor tasks run in a loop while the connector is running and repeatedly call the abstract accept(int)
method.
The implementation of the accept method must:
- block waiting for new connections
- accept the connection (eg socket accept)
- perform any configuration of the connection (eg. socket configuration)
- call the
getDefaultConnectionFactory()
ConnectionFactory.newConnection(Connector, org.eclipse.jetty.io.EndPoint)
method to create a new Connection instance.
-
Nested Class Summary
Nested classes/interfaces inherited from class org.eclipse.jetty.util.component.AbstractLifeCycle
AbstractLifeCycle.AbstractLifeCycleListener, AbstractLifeCycle.StopException
Nested classes/interfaces inherited from interface org.eclipse.jetty.util.component.Container
Container.InheritedListener, Container.Listener
Nested classes/interfaces inherited from interface org.eclipse.jetty.util.component.Dumpable
Dumpable.DumpableContainer
Nested classes/interfaces inherited from interface org.eclipse.jetty.util.component.Graceful
Graceful.Shutdown, Graceful.ThrowingRunnable
Nested classes/interfaces inherited from interface org.eclipse.jetty.util.component.LifeCycle
LifeCycle.Listener
-
Field Summary
-
Constructor Summary
ConstructorDescriptionAbstractConnector
(Server server, Executor executor, Scheduler scheduler, ByteBufferPool pool, int acceptors, ConnectionFactory... factories) -
Method Summary
Modifier and TypeMethodDescriptionprotected abstract void
accept
(int acceptorID) void
addConnectionFactory
(ConnectionFactory factory) void
void
void
protected void
doStart()
Starts the managed lifecycle beans in the order they were added.protected void
doStop()
Stops the managed lifecycle beans in the reverse order they were added.int
int
<T> T
getConnectionFactory
(Class<T> factoryType) getConnectionFactory
(String protocol) Get theHttpChannel.Listener
s added to the connector as a single combined Listener.long
getName()
Get the connector name if set.long
protected boolean
protected void
boolean
boolean
void
join()
void
join
(long timeout) protected void
onEndPointClosed
(EndPoint endp) protected void
onEndPointOpened
(EndPoint endp) removeConnectionFactory
(String protocol) void
setAccepting
(boolean accepting) void
setAcceptorPriorityDelta
(int acceptorPriorityDelta) Set the acceptor thread priority delta.void
setConnectionFactories
(Collection<ConnectionFactory> factories) void
setDefaultProtocol
(String defaultProtocol) void
setIdleTimeout
(long idleTimeout) Sets the maximum Idle time for a connection, which roughly translates to theSocket.setSoTimeout(int)
call, although with NIO implementations other mechanisms may be used to implement the timeout.void
Set a connector name.void
setShutdownIdleTimeout
(long idle) shutdown()
Shutdown the component.toString()
Methods inherited from class org.eclipse.jetty.util.component.ContainerLifeCycle
addBean, addBean, addEventListener, addManaged, contains, destroy, dump, dump, dump, dumpObjects, dumpStdErr, getBean, getBeans, getBeans, getContainedBeans, getContainedBeans, isAuto, isManaged, isUnmanaged, manage, removeBean, removeBeans, removeEventListener, setBeans, start, stop, unmanage, updateBean, updateBean, updateBeans, updateBeans
Methods inherited from class org.eclipse.jetty.util.component.AbstractLifeCycle
getEventListeners, getState, getState, isFailed, isRunning, isStarted, isStarting, isStopped, isStopping, setEventListeners, start, stop
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
Methods inherited from interface org.eclipse.jetty.server.Connector
getTransport
Methods inherited from interface org.eclipse.jetty.util.component.Container
addBean, addBean, addEventListener, getBean, getBeans, getBeans, getCachedBeans, getContainedBeans, getEventListeners, isManaged, manage, removeBean, removeEventListener, unmanage
Methods inherited from interface org.eclipse.jetty.util.component.Dumpable.DumpableContainer
isDumpable
Methods inherited from interface org.eclipse.jetty.util.component.LifeCycle
addEventListener, isFailed, isRunning, isStarted, isStarting, isStopped, isStopping, removeEventListener, start, stop
-
Field Details
-
LOG
protected static final org.slf4j.Logger LOG
-
-
Constructor Details
-
AbstractConnector
public AbstractConnector(Server server, Executor executor, Scheduler scheduler, ByteBufferPool pool, int acceptors, ConnectionFactory... factories) - Parameters:
server
- The server this connector will be added to. Must not be null.executor
- An executor for this connector or null to use the servers executorscheduler
- A scheduler for this connector or null to either aScheduler
set as a server bean or if none set, then a newScheduledExecutorScheduler
instance.pool
- A buffer pool for this connector or null to either aByteBufferPool
set as a server bean or none set, the newArrayByteBufferPool
instance.acceptors
- the number of acceptor threads to use, or -1 for a default value. If 0, then no acceptor threads will be launched and some other mechanism will need to be used to accept new connections.factories
- The Connection Factories to use.
-
-
Method Details
-
getHttpChannelListeners
Get theHttpChannel.Listener
s added to the connector as a single combined Listener. This is equivalent to a listener that iterates over the individual listeners returned fromgetBeans(HttpChannel.Listener.class);
, except that:- The result is precomputed, so it is more efficient
- The result is ordered by the order added.
- The result is immutable.
- Returns:
- An unmodifiable list of EventListener beans
- See Also:
-
getServer
-
getExecutor
- Specified by:
getExecutor
in interfaceConnector
- Returns:
- the
Executor
used to submit tasks
-
getByteBufferPool
- Specified by:
getByteBufferPool
in interfaceConnector
- Returns:
- the
ByteBufferPool
to acquire buffers from and release buffers to
-
getIdleTimeout
- Specified by:
getIdleTimeout
in interfaceConnector
- Returns:
- the max idle timeout for connections in milliseconds
-
setIdleTimeout
public void setIdleTimeout(long idleTimeout) Sets the maximum Idle time for a connection, which roughly translates to the
Socket.setSoTimeout(int)
call, although with NIO implementations other mechanisms may be used to implement the timeout.The max idle time is applied:
- When waiting for a new message to be received on a connection
- When waiting for a new message to be sent on a connection
This value is interpreted as the maximum time between some progress being made on the connection. So if a single byte is read or written, then the timeout is reset.
- Parameters:
idleTimeout
- the idle timeout
-
setShutdownIdleTimeout
public void setShutdownIdleTimeout(long idle) -
getShutdownIdleTimeout
public long getShutdownIdleTimeout() -
getAcceptors
- Returns:
- Returns the number of acceptor threads.
-
doStart
Description copied from class:ContainerLifeCycle
Starts the managed lifecycle beans in the order they were added.- Overrides:
doStart
in classContainerLifeCycle
- Throws:
AbstractLifeCycle.StopException
- If thrown, the lifecycle will immediately be stopped.Exception
- If there was a problem starting. Will cause a transition to FAILED state
-
interruptAcceptors
protected void interruptAcceptors() -
shutdown
Description copied from interface:Graceful
Shutdown the component. When this method returns, the component should not accept any new load. -
isShutdown
public boolean isShutdown()- Specified by:
isShutdown
in interfaceGraceful
- Returns:
- True if
Graceful.shutdown()
has been called.
-
doStop
Description copied from class:ContainerLifeCycle
Stops the managed lifecycle beans in the reverse order they were added.- Overrides:
doStop
in classContainerLifeCycle
- Throws:
Exception
- If there was a problem stopping. Will cause a transition to FAILED state
-
join
- Throws:
InterruptedException
-
join
- Throws:
InterruptedException
-
accept
- Throws:
IOException
InterruptedException
-
isAccepting
public boolean isAccepting()- Returns:
- Is the connector accepting new connections
-
setAccepting
public void setAccepting(boolean accepting) -
getConnectionFactory
- Specified by:
getConnectionFactory
in interfaceConnector
- Parameters:
protocol
- the next protocol- Returns:
- the
ConnectionFactory
associated with the protocol name
-
getConnectionFactory
- Specified by:
getConnectionFactory
in interfaceConnector
-
addConnectionFactory
-
addFirstConnectionFactory
-
addIfAbsentConnectionFactory
-
removeConnectionFactory
-
getConnectionFactories
- Specified by:
getConnectionFactories
in interfaceConnector
-
setConnectionFactories
-
clearConnectionFactories
public void clearConnectionFactories() -
getAcceptorPriorityDelta
@ManagedAttribute("The priority delta to apply to acceptor threads") public int getAcceptorPriorityDelta() -
setAcceptorPriorityDelta
public void setAcceptorPriorityDelta(int acceptorPriorityDelta) Set the acceptor thread priority delta.This allows the acceptor thread to run at a different priority. Typically this would be used to lower the priority to give preference to handling previously accepted connections rather than accepting new connections
- Parameters:
acceptorPriorityDelta
- the acceptor priority delta
-
getProtocols
- Specified by:
getProtocols
in interfaceConnector
-
getDefaultProtocol
-
setDefaultProtocol
-
getDefaultConnectionFactory
- Specified by:
getDefaultConnectionFactory
in interfaceConnector
- Returns:
- the default
ConnectionFactory
associated with the default protocol name
-
handleAcceptFailure
-
getConnectedEndPoints
- Specified by:
getConnectedEndPoints
in interfaceConnector
- Returns:
- immutable collection of connected endpoints
-
onEndPointOpened
-
onEndPointClosed
-
getScheduler
- Specified by:
getScheduler
in interfaceConnector
- Returns:
- the
Scheduler
used to schedule tasks
-
getName
Description copied from interface:Connector
Get the connector name if set.A
ContextHandler
may be configured with virtual hosts in the form "@connectorName" and will only serve requests from the named connector. -
setName
Set a connector name. A context may be configured with virtual hosts in the form "@contextname" and will only serve requests from the named connector,- Parameters:
name
- A connector name.
-
toString
- Overrides:
toString
in classAbstractLifeCycle
-