Max conns Option

Updated in release: 8.0

The  option is available for various components,  specifying for those components the maximum number of concurrent  connections permitted (typically to a server process). Setting  to higher values allows more connections, but at the potential cost of decreased performance for each individual connection.

Use with smpp_server
 The SMPP Server option,  , specifies the maximum number of concurrent, inbound TCP connections to allow for this SMPP Server instantiation. By default, a value of 7,000 connections is used. Note that this option will be ignored if it exceeds the global  setting.

The default value in this context is: 7000

See also:
 * SMS smpp_server options

Use with smpp_relay
 The SMPP Relay option, , specifies the maximum number of concurrent, inbound TCP connections to allow for this SMPP Relay instantiation. By default, a value of 7,000 connections is used. Note that this option will be ignored if it exceeds the global  setting.

The default value in this context is: 7000

See also:
 * SMS smpp_relay options

Use with sms_gateway
 The SMS gateway option, , specifies the maximum number of concurrent, inbound TCP connections to allow across all SMPP relay and server instantiations. A value of 0 (zero) indicates that there is no global limit on the number of connections. There may, however, be per relay or server limits imposed by a given relay or server instantiation; see the  and   values.

The default value in this context is: 10000

See also:
 * SMS gateway options

max_conns Dispatcher option (non-negative integer)
 The   Dispatcher option  specifies the maximum number of concurrent connections handled by a single server process (Worker Process). When the maximum number of concurrent sessions is reached, the server process stops listening for new connections. When all currently open connections are closed, the process will exit. Setting  sets a global default, which may be overridden for specific services by setting   under that , e.g.,   .

Prior to Messaging Server 7.0.5, the default value was 10, but initial configuration set the option explicitly to 50. As of 7.0.5, the default value is now 50. In Messaging Server 7.2 and earlier, the maximum possible value for this option was unconditionally 50, with attempts to set a value higher  than 50 resulting in the value of 50 being used. As of Messaging Server 7.3, the maximum of 50 is only enforced on 32 bit platforms; 64 bit platforms allow any value.

Setting  to higher values allows more connections, but at the potential cost of decreased performance for each individual connection. If it is set to 1, then for every incoming client connection, only one server process will be used. When the client shuts down, the server process will also exit. Note that the  value times the   value controls the  maximum number of simultaneous connections that can be accepted.

The default value in this context is: 50

See also:
 * Dispatcher options
 * max_procs Option
 * Creation and expiration of Dispatcher Worker Processes

Dispatcher service options: max_conns (non-negative integer)
 The  Dispatcher    option,    , specifies the maximum number of concurrent connections handled by a single server process (Worker Process) for this. When the maximum number of concurrent sessions is reached, the server process stops listening for new connections. When all currently open connections are closed, the process will exit.

Such a per-  setting overrides any global Dispatcher setting.

The default value for this option is 50. In Messaging Server 7.0.2 and earlier as well as legacy 32 bit platforms, the maximum possible value for this option was unconditionally 50, with attempts to set a value higher than 50 resulting in the value of 50 being used.

In principle, for services running under the Dispatcher where the server image is not multithreaded, this option must be set to 1. However, the main Dispatcher services of interest, including the MTA&#x27;s SMTP server and  LMTP server,  are multi-threaded and therefore capable of handling multiple clients. For such multithreaded servers, the choice of setting for this option is mainly a performance issue relating to the number of processes and the size of the process virtual address space. Setting  to higher values allows more connections, but at the potential cost of decreased performance for each individual connection. If it is set to 1, then for every incoming client connection, only one server process will be used. When the client shuts down, the server process will also exit. Note that the  value times the   value controls the  maximum number of simultaneous connections that can be accepted.

The default value in this context is: 50

See also:
 * Service group
 * Dispatcher options
 * max_procs Option
 * Creation and expiration of Dispatcher Worker Processes
 * TCPIP channels
 * LMTP back end TCPIP channel
 * image Option

Use with metermaid_client
 The    MeterMaid client option, , specifies how many concurrent connections can be established to MeterMaid from a single process.

The default value in this context is: 5

See also:
 * metermaid_client options

Use with isc_client
 The  isc_client option specifies the maximum number of connections that are permitted from a single LMTP process to the ISC server. Starting with 8.0.2.2, this option is preferred over the  option.

The default value in this context is: 5

See also:
 * ISC options

Use with remote_server
 The  MeterMaid client    option,   ,  specifies how many concurrent connections can be established to the specified remote server from a single process.

The default value in this context is: 3

See also:
 * remote_server
 * metermaid_client options

Use with pmxbl
 RESTRICTED: The  option specifies how many concurrent connections can be established to the PureMessage IP Blocker service from a single process. The default is ; attempting to set a value greater than   will result in the default value of   being used.

The default value in this context is: 3

See also:
 * max_procs Option
 * pmxbl options

See also:
 * Dispatcher options
 * Service group
 * metermaid_client options
 * remote_server
 * pmxbl options
 * SMS gateway options
 * SMS smpp_relay options
 * SMS smpp_server options