Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 535.7K On-Premises Infrastructure
- 138.1K Analytics Software
- 38.6K Application Development Software
- 5.6K Cloud Platform
- 109.3K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
OCIAQDeq fails to deque existing messages

3004
Member Posts: 204,171 Green Ribbon
Environment:
Oracle Server 8.1.6 WinNT
Oracle Client 8.1.7 WinNT
point-to-point queue
AQDEQ options:
DEQ_MODE = OCI_DEQ_REMOVE
VISIBILITY = OCI_DEQ_ON_COMMIT
WAIT = OCI_DEQ_WAIT_FOREVER
Problem:
Sometimes the queue consumer application blocks on OCIAQDeq when there is an existing message in the queue or a message has just been enqued.
However , if another message is enqued , OCIAQDeq returns both the first and the second message.
I never observed this with more than one message.
Oracle Server 8.1.6 WinNT
Oracle Client 8.1.7 WinNT
point-to-point queue
AQDEQ options:
DEQ_MODE = OCI_DEQ_REMOVE
VISIBILITY = OCI_DEQ_ON_COMMIT
WAIT = OCI_DEQ_WAIT_FOREVER
Problem:
Sometimes the queue consumer application blocks on OCIAQDeq when there is an existing message in the queue or a message has just been enqued.
However , if another message is enqued , OCIAQDeq returns both the first and the second message.
I never observed this with more than one message.
Comments
-
Try using the OCI_DEQ_FIRST_MSG navigation mode (OCI_ATTR_NAVIGATION)
This discussion has been closed.