Transactions Cancelled Due to an Abrupt Shutdown of the MPOS and ORPOS Client Applications Are Sent to QueueException Directory (Doc ID 1682003.1)

Last updated on MAY 02, 2016

Applies to:

Oracle Retail Point-of-Service - Version 13.4 to 14.0.1.1 [Release 13.4 to 14.0]
Information in this document applies to any platform.

Symptoms

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.

  1. Transaction 0004 is a suspended transaction with an item added.
  2. Transaction 0005 is a cancelled transaction due to shutting down the MPOS app at the Tender Auth offline screen. 
  3. Restart the app and complete the suspended transaction – 0006.
  4. 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)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms