How to Avoid Staged Messages Pileup
Hi,
We are experiencing a congestion in the Staged Messages table in our production environment.
On initial analysis it seems to be because the transactions from POS (a lot) needs to be consumed first before the polling timers for other messages (such as Item, ItemLoc, Vendor etc) are processed.
I had a look at the processtagedmessages.sh batch in Operations Guide. Will scheduling the batch intelligently help overcome this issue?
Does someone in this forum experience similar issues and if yes could you use processtagemessages.sh batch for resolving the same?
All thoughts are welcome,
Regards,
0