Ejournals Stop Flowing to CentralOffice When POS server is Restarted

(Doc ID 1395953.1)

Last updated on NOVEMBER 12, 2015

Applies to:

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


When Oracle Retail Back Office (ORBO) is restarted while Oracle Retail Central Office (ORCO) & Oracle Retail Point of Service (ORPOS) are running,  e-journals stop flowing to ORCO from ORPOS and the following error observed on the ORPOS log.


ERROR 2011-07-06 06:34:30,203 1742063 (JournalQueueMonitor-10:com.extendyourstore.foundation.manager.journal.QueuedJournalMonitor):

Class: com.extendyourstore.foundation.tour.gate.ValetException(Revision 3) @30831172: Technician JMSJournalTechnician was unable to complete its task.
Nested exception--->javax.jms.JMSException: enqMessage
at com.extendyourstore.foundation.tour.manager.Technician.receiveValet(Technician.java:755)
at com.extendyourstore.foundation.comm.proxy.rmi.RMICommProxy.remoteTransport(RMICommProxy.java:262)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Steps To Reproduce:

1. Start ORCO, ORBO and ORPOS
2. Login to ORPOS
3. Perform a sale transaction of Item 1234 tendered with Cash
4. Observe that corresponding tables TR_TRN & JL_ENR are updated with the transaction on BO and CO
5. Stop the Back Office instance
6. Start the Back Office instance
7. Perform a sale transaction of Item:4321 tendered with Cash

Ejournal records are not available in CO.


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