IBM MQ · Rate Limits

Ibm Mq Rate Limits

IBM MQ does not publish per-second HTTP rate limits in the same way as SaaS APIs; throughput on managed MQ on Cloud is governed by the chosen reserved-capacity tier (Small / Medium / Large) and the queue manager's configured maximum channels, MQI bind connections, and message size limits. On-premises MQ throughput is bounded by the host hardware, channel definitions (MAXMSGS, SHARECNV), and queue depth settings. Limits captured here describe the documented governance surfaces rather than fabricated TPS numbers.

Ibm Mq Rate Limits is the machine-readable rate-limit profile for IBM MQ on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring varies, concurrent_connections, and bytes_per_message.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Async, Enterprise, Integration, Messaging, and Middleware.

3 Limits Throttle: 429
AsyncEnterpriseIntegrationMessagingMiddlewareQueueRate Limiting

Limits

IBM MQ on Cloud Reserved Capacity throughput deployment
varies
governed by Small / Medium / Large reserved-capacity tier
Queue manager channel limits queue-manager
concurrent_connections
governed by queue-manager MAXCHANNELS / MAXACTIVECHANNELS / SHARECNV
Message size queue
bytes_per_message
governed by queue MAXMSGL (default 4 MB, max 100 MB)

Policies

Backoff Strategy
Clients receiving 2033 (MQRC_NO_MSG_AVAILABLE) or 2009 (MQRC_CONNECTION_BROKEN) should reconnect with exponential backoff; HTTP clients should honor 429 / 503 with exponential backoff and jitter.
Channel Heartbeats
Channels use HBINT to detect inactivity; long-running consumers should tune heartbeat and keepalive parameters to avoid spurious disconnects under load.
Capacity Sizing
For IBM MQ on Cloud, pick a Reserved Capacity tier (Small / Medium / Large) sized to peak throughput; tier upgrades are scheduled rather than instant.
Fair Use
Even on dedicated deployments, sustained traffic that materially impacts shared infrastructure may be subject to operational throttling.