Price Changes Remain in Conflict Checking Status With "Fatal Error ! Service Lookup Failed" Error
(Doc ID 2441635.1)
Last updated on AUGUST 03, 2020
Applies to:Oracle Retail Price Management - Version 16.0.1 and later
Information in this document applies to any platform.
The issue described in this document is known to Oracle, and a fix already scheduled for future release.
This article will be updated as official patch information becomes available.
Unable to approve the Prices Changes (PCs) and they keep remain the Conflict Checking status.
Error while lookingup home interface(com.retek.rib.app.messaging.publisher.service.ApplicationMessagePublisher)
java.lang.RuntimeException: Unable to associate remote jndi context to current thread.
ERROR Fatal Error ! Service lookup failed due to ( Fatal Error while calling remote Ejb (Class).
This may be due to ANY one of these reasons
. JNDI configuration may be incorrect please check the file (retail/remote_service_locator_info_*.xml).
. Remote application or the Hosting app server may be down.
. Network connectivity failure.
ERROR RIB Message Payloads under Transaction ID not published due to class com.retek.platform.exception.RetekUnknownSystemException: oracle.retail.integration.framework.common.service.exception.ServiceCreationException: Service lookup failed.
Steps to Reproduce
The issue can be reproduced at will with the following steps:
1. Generate a PC.
2. Approve it.
3. Notice that it is still in the Conflict Checking status.
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