Error "Could not open JPA EntityManager for transaction" When Starting P6 Team Member if the P6 EPPM Configuration Has 10 or More Database Instances (Doc ID 2972839.1)

Last updated on OCTOBER 16, 2023

Applies to:

Symptoms

When a P6 EPPM configuration has 10 or more database instances, the startup of P6 Team Member can fail with the following exception:

Could not open JPA EntityManager for transaction; nested exception is javax.persistence.PersistenceException: java.lang.NullPointerException

The following error can also be seen in the <P6 EPPM home>\tmws\p6tmweb.log;

SEVERE: Failed creating datasource for <JDBCSTRING>
oracle.ucp.UniversalConnectionPoolException: Universal Connection Pool not found in Universal Connection Pool Manager. Register the Universal Connection Pool with Universal Connection Pool Manager

The issue can be reproduced at will with the following steps:

1. Access the P6 Administrator application using ONE of the following methods:
   • In a web browser, go to http://<P6 EPPM server>:<P6 Web port>/p6/action/adminconfig (ex. http://example.com:8203/p6/action/adminconfig) and login with a P6 admin-superuser account.
   • Navigate to the <P6 EPPM home>\p6 directory (ex. C:\P6EPPM_1\p6), launch adminpv.cmd, and login with the privileged schema user (default privuser) credentials.
2. Expand the (configuration used by P6 Team Member) > Database section.
3. Right-click Instance[1] and select Duplicate. (Note that a new Instance[#] section will be created)
4. Repeat Step 3 to create at least 10 total Instances.
5. Click Save changes then close the P6 Administrator.
6. Stop and Start the WLS Managed Server hosting Team Member:
   1. Navigate to the <Oracle Middleware home>\wlserver\user_projects\domains\base_domain\bin directory.
      
   2. Run stop_weblogic.bat then start_weblogic.bat to stop and start WebLogic Server.
7. Note the exception that occurs while the P6 Managed Server is starting the P6 Team Member deployment.

Changes

Cause