Transactions Cancelled Due to an Abrupt Shutdown of the MPOS and ORPOS Client Applications Are Sent to QueueException Directory
Last updated on OCTOBER 04, 2017
Applies to:Oracle Retail Point-of-Service - Version 13.4 to 22.214.171.124 [Release 13.4 to 14.0]
Information in this document applies to any platform.
When attempting to persist a transaction cancelled due to an abrupt shutdown of the Mobile Point of Service (MPOS) or POS client, the following 'integrity constraint violation' error occurs in the QueueException folder on the Point of Service (POS) server:
Steps to Reproduce :
Pre-requisite: Business Date is set (in domain.properties) to be included in the transaction sequence number.
- Transaction 0004 is a suspended transaction with an item added.
- Transaction 0005 is a cancelled transaction due to shutting down the MPOS app at the Tender Auth offline screen.
- Restart the app and complete the suspended transaction – 0006.
- Start another transaction. Add an item and cancel the transaction – 0007.
Note that after a few minutes a QueueException is file created on the POS Server (C:\OracleRetailStore\Server\pos\bin\QueueException\01111111051314210626.txt)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms