My Oracle Support Banner

javax.naming.NameNotFoundException: Name jdbc not found in context "java:comp/env" error on Websphere startup. (Doc ID 2646746.1)

Last updated on MARCH 10, 2020

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 8.0.7 version, Administration_OFSS

After OFSAA services and Websphere restart, the following error occurs.

ERROR
-----------------------
OFSAA.log
[2020-01-30 07:42:07,076] [ERROR] [WEB] [NA] [NA] DB Connection failed for DBName: CONFIG, DBType: ORACLE
javax.naming.ConfigurationException: A JNDI operation on a "java:" name cannot be completed because the server runtime is not able to associate the operation's thread with any J2EE application component. This condition can occur when the JNDI client using the "java:" name is not executed on the thread of a server application request. Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names.
at com.ibm.ws.naming.java.javaURLContextImpl.throwExceptionIfDefaultJavaNS(javaURLContextImpl.java:522) ~[com.ibm.ws.runtime.jar:?]
at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:552) ~[com.ibm.ws.runtime.jar:?]
at com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLContextImpl.java:481) ~[com.ibm.ws.runtime.jar:?]
at com.ibm.ws.naming.urlbase.UrlContextImpl.lookup(UrlContextImpl.java:1314) ~[com.ibm.ws.runtime.jar:?]
at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:387) ~[com.ibm.ws.runtime.jar:?]
at com.ofs.aai.database.generic.jndi.WebsphereDataSource.getConnection(WebsphereDataSource.java:92) ~[aai-core.jar:?]
at com.ofs.aai.database.impl.GenericOFSAAConnectionFactory.getConnection(GenericOFSAAConnectionFactory.java:389) [aai-core.jar:?]
at com.ofs.aai.database.impl.GenericOFSAAConnectionFactory.getConnection(GenericOFSAAConnectionFactory.java:294) [aai-core.jar:?]
at com.ofs.aai.database.impl.GenericOFSAAConnectionFactory.getConfigConnection(GenericOFSAAConnectionFactory.java:106) [aai-core.jar:?]
at com.oracle.aai.redaction.RedactionHelper.getConfigConnection(RedactionHelper.java:220) [aai-redaction-client.jar:?]
at com.oracle.aai.redaction.RedactionHelper.isRedactionEnabled(RedactionHelper.java:54) [aai-redaction-client.jar:?]
at com.oracle.aai.redaction.RedactionClient.getDataAccess(RedactionClient.java:74) [aai-redaction-client.jar:?]
at com.ofss.fccm.fraud.db.DBConnection.getConnection(DBConnection.java:67) [RealTimeFraud.jar:?]
at com.ofss.fccm.fraud.db.DBConnection.executeQuery(DBConnection.java:84) [RealTimeFraud.jar:?]
at com.ofss.fccm.fraud.main.ProcessCronJob.run(ProcessCronJob.java:36) [RealTimeFraud.jar:?]
at java.util.TimerThread.mainLoop(Timer.java:566) [?:1.8.0]
at java.util.TimerThread.run(Timer.java:516) [?:1.8.0]
Caused by: javax.naming.NameNotFoundException: Name jdbc not found in context "java:comp/env".


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Try to restart OFSAA services and check the logs

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue,there is no business impact but the logs are getting filled up with exceptions.

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.