My Oracle Support Banner

Ejournal Transactions Are Not Added to Journal Queue Due to 'NullPointerException' (Doc ID 1053702.1)

Last updated on MARCH 16, 2019

Applies to:

Oracle Retail Point-of-Service - Version 12.0 to 13.1 [Release 12.0 to 13.1]
Information in this document applies to any platform.


When attempting to add journals to the journal queue, the Point Of Service (POS) server is consistently logging POSJMSJournal errors similar to the following:

at com.extendyourstore.pos.manager.journal.POSJMSJournalHandler.addEntry( Code))
at Code))
at Code))
at Code))
at Code))
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke( Code))
at java.lang.reflect.Method.invoke( Code))
at sun.rmi.server.UnicastServerRef.dispatch( Code))
at sun.rmi.transport.Transport$ Code))
at Method)
at Code))
at sun.rmi.transport.Transport.serviceCall( Code))
at sun.rmi.transport.tcp.TCPTransport.handleMessages( Code))
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleRequest( Code))
at sun.rmi.transport.tcp.TCPTransport$ Code))
at Code))

Steps to Reproduce

1. Process several transactions on POS
2. At one point when the journal transactions are added to the journal queue, the queue size continues to grow
3. Ejournals are not found in the Central Office database




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

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