weblogic.common.ResourceException With No Message When Creating A Data Source Under An Existent JNDI Node
(Doc ID 2379754.1)
Last updated on APRIL 15, 2020
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
When creating a generic JDBC DataSource and assigning it to cluster, we get an exception below. The exception does not include cause to help address issue.
As a result of this exception, the new data source is not deployed, but the issue is that this exception includes no message.
Members of cluster are located on different machines (1 machine for AS and other 2 different machines for the 2 members). Both members are up and running when the issue is replicated.
- does not happen if targeted to the AdminServer
- does not happen if JNDI name is changed to jdbc/xxx
- occurs without PSU and with latest PSU (10.3.6.0.171017 at the moment this note was written).
Previously other data sources were created.
This issue could be replicated in house with the following steps:
1- configure a domain in production mode
2- create a cluster with 2 members
3- start nodemanager
4- start the managed servers via WLS console
5- create a DS pointing to JNDI jdbc/xxx targetted to a cluster
6- restart the AdminServer
7- login to WLS console and create a second data source pointing to JNDI jdbc/xxx/Ds and targeted to the cluster, the exception is seen in output of AdminServer
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