Skip to main content
ReferenceApplies to: Unified engine deployments
[transport]

Settings

queue_capacity

Limits how many internal service requests can wait in the transport queue.
  • Default: 128
  • Type: integer; positive
Example 128 gives the queue 128 request slots. When the queue fills, senders must wait rather than keep adding work to memory.

max_message_bytes

Limits the encoded size of one message exchanged between Unified services.
  • Default: 68157440
  • Type: integer (bytes); positive
Example 68157440 allows a message up to 65 MiB. A large service response must fit this limit as well as the receiving service’s own response limit.

max_connections

Limits how many internal service connections the transport may keep open at once.
  • Default: 1024
  • Type: integer; positive
Example 1024 permits up to 1024 connections. This counts connections, not the number of requests carried by each connection.

Notifications

notifications.queue_capacity

Limits how many notification messages may wait in the notification queue.
  • Default: 8
  • Type: integer; positive
Example 8 gives the queue eight message slots. The queue’s byte limit still applies when fewer than eight large messages are waiting.

notifications.max_message_bytes

Limits how large one internal notification message may be.
  • Default: 65536
  • Type: integer (bytes); positive
Example 65536 allows a notification up to 64 KiB. Notifications use this smaller limit rather than the main service-message limit.

notifications.max_queue_bytes

Limits the combined bytes held in the notification queue.
  • Default: 262144
  • Type: integer (bytes); positive
Example 262144 gives the queue a 256 KiB total budget. Four 64 KiB messages can fill that budget before the eight-message count limit is reached.
Last modified on November 4, 2026