Last updated on SEPTEMBER 10, 2014
Applies to:Oracle TopLink - Version 10.1.3.3 to 10.1.3.5 [Release AS10gR3]
Information in this document applies to any platform.
In a Toplink 10.1.3.3 POJO production application the data caching mechanism is causing a large volume of data synchronization processes to be created and never terminated.
Those processes therefore begin to consume more and more server resources which can lead to application server hangs with a high thread count.
Numerous stack traces are logged such as the following:
Problem appears to be related to HardCacheWeakIdentityMap. This issue also occurs for Toplink 10.1.3.5.0.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms