OCI-25228
timeout or end-of-fetch during message dequeue from string.string
Cause
One of the following happened:
- The queue does not have messages to consume currently and the dequeue was attempted with no_wait
- The user-specified dequeue wait time passed.
- The end of the queue was reached but no message was retrieved.
- An external event was set to break the blocking dequeue.
Action
- Ensure the queue has the unconsumed messages before attempting dequeue.
- Try dequeue again with the appropriate WAIT_TIME.
- If the end-of-fetch has reached, then retry dequeue with the the FIRST_MESSAGE navigation option.
- Ensure the event 10852 at level 0x100000 is not set.