Menu Search

7.10. Ports

Ports provide TCP/IP connectivity for messaging and management. A port is defined to use a protocol. This can be an AMQP protocol for messaging or HTTP for management.

A port is defined to have one or more transports. A transport can either be plain (TCP) or SSL (TLS). When SSL is in use, the port can be configured to accept or require client authentication.

Any number of ports defined to use AMQP or HTTP protocols can be defined.

Ports can only be managed by the HTTP management channel.

7.10.1. Context

  • qpid.port.max_open_connections. The default maximum number of concurrent connections supported by an AMQP port.

  • qpid.port.amqp.acceptBacklog. The backlog is the maximum number of pending connections that may be queued by the AMQP port. Once the queue is full, further connections will be refused. This is a request to the operating system which may or may not be respected. The operating system itself may impose a ceiling. [8]

  • qpid.port.heartbeatDelay. For AMQP 0-8..0-10 the default period with which Broker and client will exchange heartbeat messages (in seconds). Clients may negotiate a different heartbeat frequency or disable it altogether. For AMQP 1.0 this setting controls the incoming idle timeout only. A value of 0 disables.

7.10.2. Attributes

  • Name the port.

  • Port number.

  • Binding address. Used to limit port binding to a single network interface.

  • Authentication Provider. The authentication provider used to authenticate incoming connections.

  • Protocol(s). A list of protocols to be supported by the port. For messaging choose one or more AMQP protocols. For management choose HTTP.

  • Transports. A list of transports supported by the port. For messaging or HTTP management chose TCP, SSL or both.

  • Enabled/Disabled Cipher Suites. Allows cipher suites supported by the JVM to be enabled or disabled. The cipher suite names are those understood by the JVM.

    SSLv3 is disabled by default.

  • Keystore. Keystore containing the Broker's private key. Required if SSL is in use.

  • Want/Need Client Auth. Client authentication can be either accepted if offered (want), or demanded (need). When Client Certificate Authentication is in use a Truststore must be configured. When using Client Certificate Authentication it may be desirable to use the External Authentication Provider.

  • Truststore. Trust store contain an issuer certificate or the public keys of the clients themselves if peers only is desired.

  • Maximum Open Connections. AMQP ports only. Limits the number of connections that may be open at any one time.

  • Thread pool size. AMQP ports only. Number of worker threads used to process AMQP connections during connection negotiation phase.

    Defaults to 8.

  • Number of selectors. AMQP ports only. Number of worker threads used from the thread pool to dispatch I/O activity to the worker threads.

    Defaults to one eighth of the thread pool size. Minimum 1.

7.10.3. Children

  • Connection

7.10.4. Lifecycle

Not supported


When updating an existing port, changes to SSL settings, binding address and port numbers do not become effective until the Broker is restarted.

[8] Some Linux distributions govern the ceiling with a sysctl setting net.core.somaxconn.