Out Of Memory By Too Much T4CStatements
(Doc ID 3015620.1)
Last updated on APRIL 09, 2024
Applies to:
JDBC - Version 19.19 and laterInformation in this document applies to any platform.
Symptoms
While having an application running in Payara JEE Container, a scheduler starts a thread every 5 seconds that works through a two-column table and updates 1000 rows before terminating. The application uses Eclipse Link JPA implementation.
Using different database connection pools gives different results:
* Switching of Payara internal pooling and activating Oracle UCP pooling, the application is observed to run out of memory after 10 minutes
* Using Payara internal connection pooling the error takes longer to occur.
From a heap dump, 5 connections in UCP were seen, but only one has 90% of the memory allocated by holding a reference to 492362 T4CStatements.
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 |
Cause |
Solution |
References |