Skip to content

Commit 3d68246

Browse files
Txeventq message operations (#1010)
1 parent 220dafc commit 3d68246

File tree

4 files changed

+488
-3
lines changed

4 files changed

+488
-3
lines changed

docs-source/transactional-event-queues/content/getting-started/_index.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,9 @@ This module will cover the following key topics:
2020

2121
## Message Operations
2222
- Producing and consuming messages
23-
- Implementing message selectors and rules
24-
- Handling message delay, expiration, and priority
23+
- Message expiry and exception queues
24+
- Message Delay
25+
- Message Priority
2526

2627
## Advanced Features
2728
- Transactional messaging: Combining messaging and DML in a single transaction

docs-source/transactional-event-queues/content/getting-started/core-concepts.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,11 @@ Transactional Event Queues support various [message payload types](https://docs.
4646

4747
Understanding these payload types is crucial for designing efficient and effective messaging solutions. The choice of payload type impacts how you interact with the queue, the kind of data you can store, and how that data is processed. Let's explore the available payload types and their use cases.
4848

49+
> Attempting to produce a message of the wrong payload type may result in the following error:
50+
>
51+
>
52+
> **ORA-25207: enqueue failed, queue <schema>.<queue> is disabled from enqueueing**
53+
4954
#### DBMS_AQADM.JMS_TYPE
5055

5156
The JMS (Java Message Service) payload type is ideal for applications using JMS, as it provides a highly scalable API for asynchronous messaging.

0 commit comments

Comments
 (0)