SOA 11g: Data Source Failing with, 'javax.naming.NameNotFoundException' (Doc ID 1536862.1)

Last updated on APRIL 28, 2016

Applies to:

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

Goal

 

This document can be usefull for the following situations:

  • You cannot create a Data Source in your environment and see the following error in the log:
Exception Description: Cannot acquire data source [jdbc/<DATA_SOURCE_NAME>].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.DATA_SOURCE_NAME'. Resolved 'jdbc'; remaining name 'DATA_SOURCE_NAME'.

####<Jan 30, 2013 4:54:04 AM CST> <Error> <oracle.soa.adapter> <vmohsbmbo008> <soa_server1> <weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@21535155> <<anonymous>> <> <a470942f7d81786f:1212b471:13c8b15dded:-7ffd-000000000000000e> <1359543244395> <BEA-000000> <Database Adapter OMScheduler <oracle.tip.adapter.db.InboundWork handleException> Encountered a fatal exception while polling.  Will continue polling but with minimal logging.  Please investigate the fault and manually stop polling from the console if in development and this appears to be a modeling mistake.  BINDING.JCA-11624
DBActivationSpec Polling Exception.
Query name: [XXSCHEDULE_GETHEADERSelect], Descriptor name: [XXSCHEDULE_GETHEADER.XxscheduleGetheader]. Polling the database for events failed on this iteration.
Caused by BINDING.JCA-11622
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.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot acquire data source [jdbc/<DATA_SOURCE_NAME>].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.DATA_SOURCE_NAME'. Resolved 'jdbc'; remaining name 'DATA_SOURCE_NAME'.
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.  This polling process will shut down, unless the fault is related to processing a particular row, in which case polling will continue but the row will be rejected (faulted).
.
at oracle.tip.adapter.db.exceptions.DBResourceException.createNonRetriableException(DBResourceException.java:653)
at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:619)
at oracle.tip.adapter.db.exceptions.DBResourceException.inboundReadException(DBResourceException.java:460)
...
  • In the log or out files, You found the following codes:

BINDING.JCA-11622
BINDING.JCA-11624

 

In this case the Data Source was created without a valid JNDI name.

 

Solution

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