ORPOS Client Activities Performance Degrades When Offline to the Server (Doc ID 1116958.1)

Last updated on JULY 24, 2017

Applies to:

Oracle Retail Point-of-Service - Version 12.0.9 and later
Information in this document applies to any platform.
***Checked for relevance on 01-AUG-2013***

Symptoms

When attempting to lookup items in offline mode when the Backoffice/StoreServer machine is powered off , there is a performance impact and Oracle Retail Point of Service (ORPOS) takes 45 seconds for the item to be displayed on the screen.

ERROR 2010-03-09 14:59:27,273 90897824 (TransactionQueueMonitor-3:com.extendyourstore.foundation.manager.data.DataManager):
[com.extendyourstore.foundation.manager.data.DataManager$TransactionQueueMonitor.processHeadTransaction(DataManager.java:1998)]
Class: com.extendyourstore.foundation.manager.data.DataException(Revision $Revision: 3$) @8376552: Class: com.extendyourstore.foundation.comm.CommException(Revision 3) @25315557: Unable to establish receiver for RemoteDT
Transaction Name:
Error code: [3] [A connection error occurred during database access.]
Error code (extended): [0]
Description: [Class: com.extendyourstore.foundation.comm.CommException(Revision 3) @25315557: Unable to establish receiver for RemoteDT]
Original exception: [null]


Steps to Reproduce :

  1. Power down the machine that the storeserver and Oracle Retail Back Office (ORBO) are running on.
  2. Loginto POS.
  3. Do an Item Lookup.
  4. It takes about 45 seconds for the item to be retrieved from the derby db.

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