My Oracle Support Banner

ORPOS Client Crash When Timeout Occurs Before IDDI Consumption Completes (Doc ID 2011879.1)

Last updated on JULY 27, 2020

Applies to:

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

Symptoms

The Oracle Retail Point of Service (ORPOS) client crashes when timeout occurs before IDDI consumption completes.

Prerequisites:

  1. Large amount of IDDI data exists (e.g., 1 million pricing records).
  2. Parameter TimeoutInactiveWithoutTransaction is set to 2 minutes.


Steps to Reproduce:

  1. Launch the ORPOS application.
  2. From 'Main Options' screen, flow goes to 'Data Update' screen.
  3. Upon timeout, ORPOS client crashes with log showing:

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.