CacheFullException: Cache 'tcDataBase' is at its limit of: 1000 *active* beans
(Doc ID 2399786.1)
Last updated on OCTOBER 21, 2019
Applies to:
Identity Manager - Version 11.1.2.3.0 and laterInformation in this document applies to any platform.
Symptoms
When the system is under heavy load, you may run into the CacheFullException as shown below:
weblogic.ejb20.cache.CacheFullException: Cache 'tcDataBase(Application:oim#11.1.2.0.0, EJBComponent: dataobjects-ejb.jar)' is at its limit of: 1000 *active* beans.]
at com.thortech.xl.ejb.interfaces.tcDataBaseDelegate.<init>(Unknown Source)
... 14 more
Caused by: javax.naming.NamingException [Root exception is weblogic.ejb20.cache.CacheFullException: Cache 'tcDataBase(Application: oim#11.1.2.0.0, EJBComponent: dataobjects-ejb.jar)' is at its limit of: 1000 *active* beans.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:86)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:472)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:428)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:155)
at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:88)
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:153)
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:178)
... 15 more
Caused by: weblogic.ejb20.cache.CacheFullException: Cache 'tcDataBase(Application: oim#11.1.2.0.0, EJBComponent: dataobjects-ejb.jar)' is at its limit of: 1000 *active* beans.
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 |