Why AnswerFlowEditor Instance (with Tomcat server on Linux) Threw Datasource Error After Applied OK v8.6.1 Rollup Patch? (Doc ID 2275873.1)

Last updated on JUNE 19, 2017

Applies to:

Oracle Knowledge - Version 8.6 and later
Information in this document applies to any platform.

Symptoms

After applied OK v8.6.1 Rollup patch to the OK v8.6.0 GA AnswerFlow (with Tomcat server on Linux), you are getting the error below when hitting the AF Editor homepage.

Exception Description: Cannot acquire data source [jdbc/answerFlow].
Internal Exception: javax.naming.NameNotFoundException: Name [jdbc/answerFlow] is not bound in this Context. Unable to find [jdbc].
  at org.eclipse.persistence.exceptions.ValidationException.cannotAcquireDataSource(ValidationException.java:497)
  at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:109)
  at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
  at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:584)
  at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206)
  at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
  ... 108 more
Caused by: javax.naming.NameNotFoundException: Name [jdbc/answerFlow] is not bound in this Context. Unable to find [jdbc].
  at org.apache.naming.NamingContext.lookup(NamingContext.java:825)
  at org.apache.naming.NamingContext.lookup(NamingContext.java:159)
  at org.apache.naming.SelectorContext.lookup(SelectorContext.java:133)
  at javax.naming.InitialContext.lookup(InitialContext.java:415)
  at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:103)

Cause

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