Oracle Cloud Infrastructure Documentation

Asynchronous Message Queue Depth

This section provides details about the asynchronous messages queue depth available with the specific message pack assigned to your Oracle Integration instance.

The following formula is used to calculate the asynchronous message queue depth:
number_of_messages_per_hour * 10
For example, 5,000 messages per hour multiplied by 10 gives you a limit of 50,000 messages.
5000 * 10 = 50000

This limit enables your instance to handle a spike of 10 times the usual number of requests, meaning you have a 10-hour backlog. A small cushion is added to this limit to ensure that message 50,001 is not rejected. However, you should focus on the limit for the number of messages you have assigned, and not rely on the small cushion.

The following table provides more specific details about message packs and queue limits.

Note

The upper queue limit is 600,000 messages. If you require more than 600,000 messages, contact Oracle.
Message Packs Messages Per Hour Queue Limit (Number of Messages * 10)
1 5,000 50,000
2 10,000 100,000
3 15,000 150,000
4 20,000 200,000
5 25,000 250,000
6 30,000 300,000
7 35,000 350,000
8 40,000 400,000
9 45,000 450,000
10 50,000 500,000
11 55,000 550,000
12 60,000 600,000
20 100,000 600,000
When the number of requests exceeds the upper limit allowed for your message pack, you receive the following error message:
{"type":"429","title":"Too busy right now. Please retry later.","detail":"The service is temporarily busy. Please retry later."}

You can monitor requests using the Async queue depth metric chart. See Available Metrics Charts.

You can create alarms on the Async queue depth metric chart that notify you when your message count exceeds a specific percentage. See Create an Alarm to Monitor Async Backlog.