My Oracle Support Banner

Intermittent Internal Exception: javax.naming.NameNotFoundException: Unable to resolve (Doc ID 2522586.1)

Last updated on JANUARY 08, 2020

Applies to:

Oracle SOA Suite - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

Customer is getting following error intermittently
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Could not create/access the TopLink Session. This session is used to connect to the datastore.

We have file processing requirement where we will read File and update to DB.

While updating the data to data base via PL/SQL procedure, getting below exception

0Exception occurred when binding was invoked.
Exception occurred during invocation of JCA binding: "JCA Binding execute of Reference operation 'InsertDNBRecords_EBS' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.6.4.v20160829-44060b6): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot acquire data source [jdbc/ebs].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.ebs'. Resolved 'jdbc'; remaining name 'ebs'.
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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
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.