Capacity

Your ExpeDat license includes a set limit on the number of simultaneous transactions supportable by each server.  Once the capacity is filled, additional transactions will be rejected with the error "Server Capacity Exceeded: Try again later".

Starting with ExpeDat 1.12 and SyncDat 1.1, clients will automatically retry after receiving a capacity error.

Only active transactions, including file transfers and file maintenance actions, count toward this capacity.  Idle clients do not contribute to the capacity limit.

Client Usage

Each MTPexpedat instance may use up to 2 capacity slots at a time: one for an active transfer and a second for browsing or file maintenance.  A third slot may be used briefly during error recovery when transferring multiple files.

Each DropDat, movedat, and syncdat instance will only use 1 capacity slot at a time.  A second slot may be used briefly during error recovery when transferring multiple files.

Monitoring Capacity

You check the current and peak server loads using the mtping utility or by looking in the logfile for 'S' status lines.  See the Monitoring section for more about monitoring the server status.

Limiting Capacity

You may reduce the capacity of the server below its licensed limit by using the Capacity configuration variable or the "-c" command line option.  This may be desirable if high traffic volumes are creating unacceptable CPU or disk I/O loads.