Cloud Admin Club

It’s a common issue, Yet confusing. a Java application, for example, an ADF application developed with JDeveloper 12c. though it is working fine in the Embedded WebLogic Server of JDeveloper, It fails when you try to deploy it or start it in a stand-alone managed server, or in your WLS Domain giving error that It misses a library adf.oracle.businesseditor, adf.oracle.domain, or adf.oracle.domain.webapp. Hence, This article explains how to define the missing library and how to solve [J2EE:160149]Unresolved application library references error message.

This solution works on:

Oracle Weblogic, Oracle Fusion Middleware 11.x, Oracle Fusion Middleware 12.1, and Oracle Fusion Middleware 12.2.

The full error message usually:

weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. 
Unresolved application library references, defined in weblogic-application.xml:[Extension-Name: adf.oracle.domain, exact-match: false]

What causes [J2EE:160149]Unresolved application library references error?

You deployed a Java application on a managed server, and your deployment needs a library that is not included in your WAR/EAR file and your managed server can’t provide access to that library. for example, there is missing ADF Runtime Libraries from the managed server where you deployed your application.

Where is adf.oracle.domain library?

The missing Java Required Files (JRF) already bundled with WebLogic Deployments as a library type, you just need to add The Managed Server you want to deploy or start your application as a Target to the missing libraries, so your application can access adf.oracle.domain library.

Usually when application complaints about ad.oracle.domain library, It does for two additional libraries adf.oracle.businesseditor and adf.oracle.domain.webapp.

SOLUTION

the following steps will allow your managed server to have access to the library:

Logon to WebLogic Console
Click on Deployments
Lookup in Deployments for the missing library name, in my case it was the following:

- adf.oracle.businesseditor(1.0,12.2.1.1.0)
- adf.oracle.domain(1.0,12.2.1.1.0)
- adf.oracle.domain.webapp(1.0,12.2.1.1.0)

and if you didn’t find it click on Customize this table and make sure to untick Exclude libraries when displaying deployments then click Apply

4. Click on library name oracle.domain(1.0,12.2.1.1.0) then Lock & Edit

5. Click on the Targets tab. Then, Select the Managed Server or Cluster where your application deployed or

6. Click on Save then Activate Changes

7. Follow same steps from 4 to 6 on following library too

- adf.oracle.businesseditor(1.0,12.2.1.1.0)
- adf.oracle.domain.webapp(1.0,12.2.1.1.0)

Important note: You may need to repeat the steps above for other libraries that I’ve not listed here, it depends on which ADF extensions your application is using.

in Conclusion, the missing adf.orac.e.domain libraries come with WebLogic. however, you can use the same procedures to investigate missing libraries and link it to your managed server, as Oracle Fusion Middleware provides a conglomerate of libraries that is common between applications.

REFERENCES

(Doc ID 947921.1)

Oracle middleware applications sometimes stop working, and generate an error message weblogic.jdbc.exetentions.poolDisabledSQLException. This article addresses this issue, showing you how to fix it.

The following scenario demonstrates the issue when Oracle web center and Oracle content server 12c where are hosted on Oracle Linux gave both error messages weblogic.common.resourceDisabledException and weblogic.jdbc.exetentions.poolDisabledSQLException.

Content Server Request Failed due poolDisabledSQLException

The development team encountered an unusual error that our Oracle WebCenter content server Console does not open, and it is generating the following error message.

Content Server Request Failed
Unable to load the user information. Encountered an exception while executing a query.
“unable to execute service method ‘getConnection’. weblogic.jdbc.exetentions.poolDisabledSQLException: weblogic.common.resourceDisabledException: pool CSDS is Suspended, cannot allocate resources to application…

Clearly, The WebCenter content server is complaining that there is a suspended data source that is mandatory for it to function properly.

weblogic.common.resourcepool.ResourceDisabledException in Logs

When you open the log file of the managed server, you will find a long detailed Java exception contains the following line.

Caused By: weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool CSDS is Suspended, cannot allocate resources to applications..
at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:269)
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:529)
at  8)

Yet, this is a misleading error message as this error message does not show the real cause. it just complains about the data source that can’t reach. But if you scrutinize the error message you will get some useful leading points. hence, to start investigating the issue.

Leading point number one: unable to execute service method ‘getConnection’

It says that web content server can’t get the database connection

Leading point number two: weblogic.jdbc.exetentions.poolDisabledSQLException

There is a data-source which has its connect pool disabled

Leading point number three: pool CSDS is Suspended

Now we are getting a thread we can follow. CSDS Data-source is suspended.

From this last point, we will investigate the reasons which caused data-source CSDS to stop working

Resume suspended data source pool

By searching the WebLogic logs you will find the same error mentioned above. To get the real cause of the problem. You need to resume the data-source so the original error will appear in the logs.

Open WebLogic console and follow these steps to resume data-source.

First, click the data-sources link under the services tree, that is located in the domain structure tree.

Second, the list of data-sources appears on the right side, click on our suspect data-source which in our case it’s CSDS.

As shown in the image below to control the data-source you need to open its configuration window

select Control tab.
Select all suspended connections (usually all the list ).
Click on the resume.

poolDisabledSQLException cause and solution!

When the data-source tries to connect to the database, Weblogic will log any errors that causing the issue. in our case, It shows an expired database username password.

<Jun 2, 2019, 7:15:13,304 PM GST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "CSDS": ORA-28001: the password has expired.>

the data-source will work properly, After resetting the password and resuming the data-source.

If you want to avoid the repetition of the issue in the future, therefore, you need to change the user’s profile setting and disable password expiration.

To conclude, This issue is a result of the data-source failure to connect to the database. If you fix that cause and resumed the data-source, the Application should resume working.

weblogic

Solved [J2EE160149] missing adf.oracle.domain