My Oracle Support Banner

WLS 10.3.5 - EjbPassivation() Fails With Entity Bean Caching When Beans Are In READY State (Doc ID 1474006.1)

Last updated on JUNE 06, 2022

Applies to:

Oracle WebLogic Server - Version 10.3.5 and later
Information in this document applies to any platform.


When stress testing an application running on top of WebLogic 10.3.5, it turns out that the idle beans never scrub the cache until it reaches max-cache-size limit.
So, the default value of 600 is not set anytime before by WebLogic, and the idle beans stay indefinite even if they are not in any transaction.

For instance, with Application cache having Max-cache-size = 250000, the following is obtained:




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.