Queue File Is Deleted and Archived, but a java.lang.NullPointerException Occurs on Client Console If Queue Is Corrupted

(Doc ID 1924486.1)

Last updated on AUGUST 17, 2016

Applies to:

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


Note: The issue described in this document is known to Oracle, and a fix already scheduled for future release.
This article will be updated as official patch information becomes available.

In Oracle Retail Point of Service (ORPOS) 13.4.x, the queue file is deleted and archived, but there is an exception on the client console when the queue file is corrupted.


Steps to Reproduce:

  1. Complete 1 normal sale transaction.
  2. Stop the client.
  3. Corrupt the transaction in the queue file.
  4. Restart the client.
  5. Queue file is deleted and archived, but there is an exception on client console:
-------------------Console Exception -------------------------------------------------
Exception in thread "TransactionQueueMonitor-1" java.lang.NullPointerException
  at oracle.retail.stores.foundation.manager.data.DataManager.executeQueuedTransaction(DataManager.java:762)
  at oracle.retail.stores.foundation.manager.data.DataManager.access$000(DataManager.java:196)
  at oracle.retail.stores.foundation.manager.data.DataManager$TransactionQueueMonitor.processHeadTransaction(DataManager.java:1918)
  at oracle.retail.stores.foundation.manager.data.DataManager$TransactionQueueMonitor.run(DataManager.java:1873)
-------------------Console Exception -------------------------------------------------



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