ORPOS Client Crash When Timeout Occurs Before IDDI Consumption Completes

(Doc ID 2011879.1)

Last updated on NOVEMBER 06, 2017

Applies to:

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


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


  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:
INFO  2015-05-01 17:35:56,357 760044
     UISubsytem mailing Letter@1189553841[name=Timeout]
INFO  2015-05-01 17:36:56,544 820231
     Bus.end: ending

INFO  2015-05-01 17:36:56,575 820262
     Dispatcher.shutdown() : CLIENT shutdown.


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