A fix is available
APAR status
Closed as program error.
Error description
During the application start, the JPA Runtime attempts to create an EntityManagerFactory for the purpose of acquiring and registering a Class Transformer. However, persistence units which use DataSources in the "java:app" namespace in <[non-]jta-data-source> do not have processing deferred as "java:comp/env" namespace. Because of this, the runtime attempts to look up the resource in the "java:app" namespace has initialized.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: CWWJP0013E message produced during * * application start * **************************************************************** * RECOMMENDATION: * **************************************************************** A CWWJP0013E message is produced when an application using JPA starts.
Problem conclusion
Applications using JPA, that are also using persistence units with <jta-data-source> and/or <non-jta-data-source> elements with ´java:app/env´ JNDI names produce a CWWJP0013E message: CWWJP0013E: The server cannot locate the java:app/env/jdbc/MyJDBC data source for the MyPersistenceUnit persistence unit because it has encountered the following exception: javax.naming.ConfigurationException: A JNDI operation on a "java:" name cannot be completed because the server runtime is not able to associate the operation's thread with any J2EE application component. This condition can occur when the JNDI client using the "java:" name is not executed on the thread of a server application request. Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names. In actuality, although this error is emitted, the JPA Runtime Integration will recover and still start the application successfully, with the Persistence Unit affected being processed as if it were a java:comp/env reference. Because this is effectively an unnecessary warning and the system recovers as if it were a java:comp/env reference, the JPA Runtime Integration that detects "java:comp/env" references was updated to also look for "java:app/env" references and thus avoid the unnecessary error signaling. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.3. For more information, see 'Recommended Updates for WebSphere Application Server': http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PH19943
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-12-05
Closed date
2020-03-16
Last modified date
2020-09-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 November 2021