Feature #717
corrid compatibility for tmqeueue
| Status: | Closed | Start date: | 07/23/2021 | |
|---|---|---|---|---|
| Priority: | Normal (Code 4) | Due date: | ||
| Assignee: | - | % Done: | 100% | |
| Category: | - | |||
| Target version: | - |
Description
Currently TPQCTL.corrid is treated as another unique message id across the whole queue space. This logic needs to be corrected, so corid basically creates a sub-queue for given queue. Thus corid may store several messages with the same corrid.
History
#1 Updated by Madars about 2 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Release notes¶
tmqueue server have been updated to handle TPQCTL.corrid as means of the sub-queue for the queue. This means that that now several messages with the same corrid may be stored in different queues in the queue space. As oposite in previous versions, corrid was meant to be another unique message identifer. When message are dequeued by TPQGETBYCORRID flag, the message ordering is kept as defined for queue: lifo or fifo.
Available from Enduro/X version 7.5.30+.
#2 Updated by Madars about 2 years ago
- Status changed from Resolved to Closed