Transactions Persisted With Previous BusinessDate After 'LookupStoreStatus CommException Failure' Occurs In POS

(Doc ID 1430364.1)

Last updated on JULY 05, 2017

Applies to:

Oracle Retail Point-of-Service - Version 12.0 and later
Information in this document applies to any platform.

Symptoms

POS fails to get the correct businessdate from the database after a failure in LookupStoreStatus (CommException error).  The end result is that transactions on the current business date are associated with the incorrect business date (yesterday's date).


Steps to Recreate:


1. Restart the store server
2. Press F3/POS and log in.  The first call to the database fails with CommException. When the first call is made to fetch store status, the call fails and store status must be retrieved from hard totals.  The following is the error produced:

INFO 2011-11-15 09:53:27,590 2936011271 (StaticCacheThread7:com.extendyourstore.foundation.tour.engine.Site):
[com.extendyourstore.foundation.tour.engine.Site.arrive(Site.java:253)]
Site LookupStoreStatus arrives within service SetupRegister

WARN 2011-11-15 09:53:28,637 2936012318 (StaticCacheThread7:com.extendyourstore.foundation.manager.data.DataManager):
[com.extendyourstore.foundation.manager.data.DataManager.sendTransaction(DataManager.java:453)]
Class: com.extendyourstore.foundation.manager.data.DataException(Revision $Revision: /main/9 $) @1399804783: Connection Error attempting DataTransaction transport.
Nested exception--->Class: com.extendyourstore.foundation.comm.CommException(Revision
/rgbustores_13.1x_branch/1) @248581841: RMI communication error executing valet.
Nested exception--->java.rmi.ConnectException:
Connection refused to host: NN.NN.NN.NNN; nested exception is:
java.net.ConnectException: Connection refused: connect
Transaction Name:

Error code: [3] [A connection error occurred during database access.]
Error code (extended): [0]
Description: [Connection Error attempting DataTransaction transport.; nested exception is:
RMI communication error executing valet.; nested exception is:
Connection refused to host: NN.NN.NN.NNN; nested exception is: java.net.ConnectException: Connection refused: connect]
Class: com.extendyourstore.foundation.comm.CommException(Revision /rgbustores_13.1x_branch/1) @248581841: RMI communication error executing valet.
Nested exception--->java.rmi.ConnectException: Connection refused to host: NN.NN.NN.NNN; nested exception is: java.net.ConnectException: Connection refused: connect, Continuing...trying alternates...

3. Transaction in TR_TRN is saved with the incorrect Business Date.  This causes the number in RTLOG for that business date to mismatch the count in the DCLOSE record

Changes

 

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