My Oracle Support Banner

Getting Error in JNDIConnectionFactory.getConnection After Upgrade Of OPA (Doc ID 2994366.1)

Last updated on JANUARY 31, 2024

Applies to:

Oracle Policy Automation - Version 12.2.11 and later
Information in this document applies to any platform.

Symptoms

After OPA upgrade from 12.2.11 to 12.2.33 post starting the managed server, OPA Hub deployment is not changing to active and getting following error in OPA Hub logs:


ERROR
-----------------------
com.oracle.determinations.hub.exception.HubStorageException: Error getting connection after waiting for 30000 ms
  at com.oracle.determinations.hub.storage.jdbc.JNDIConnectionFactory.getConnection(JNDIConnectionFactory.java:140)
  at com.oracle.determinations.hub.storage.jdbc.JNDIConnectionFactory.getConnection(JNDIConnectionFactory.java:67)
  at com.oracle.determinations.hub.storage.jdbc.JNDIConnectionFactory.getSQLContext(JNDIConnectionFactory.java:222)
  at com.oracle.determinations.hub.storage.jdbc.ConfigPropertyDAOImpl.getAllConfigurationProperties(ConfigPropertyDAOImpl.java:195)
  at com.oracle.determinations.hub.storage.jdbc.ConfigPropertyDAOImpl.getHubFeatureSet(ConfigPropertyDAOImpl.java:290)
  Truncated. see log file for complete stacktrace
Caused By: java.util.concurrent.TimeoutException
  at java.util.concurrent.FutureTask.get(FutureTask.java:205)
  at com.oracle.determinations.hub.storage.jdbc.JNDIConnectionFactory.getConnection(JNDIConnectionFactory.java:136)
  at com.oracle.determinations.hub.storage.jdbc.JNDIConnectionFactory.getConnection(JNDIConnectionFactory.java:67)
  at com.oracle.determinations.hub.storage.jdbc.JNDIConnectionFactory.getSQLContext(JNDIConnectionFactory.java:222)
  at com.oracle.determinations.hub.storage.jdbc.ConfigPropertyDAOImpl.getAllConfigurationProperties(ConfigPropertyDAOImpl.java:195)
  Truncated. see log file for complete stacktrace

The issue can be reproduced at will with the following steps:
1. Execute upgrade installation following steps on Intelligent Advisor Documentation Library Documentation
2. No Errors in the installation logs
3. Try to Activate OPA deployment

Changes

Upgrade from 12.2.11 to 12.2.33

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
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.