CacheFullException in WebLogic Server 8.1SP4

Hello,

in our production system based on Weblogic Portal 8.1SP4 we are experiencing
severe problems because of CacheFullExceptions lately.
This is especially problematic, since we are a Webservice Server and our
Webservice Clients do get this Exception in the Webservice answers.

Raising the max-beans-in-cache does not seem to help. The cache is already
several times higher than the actual bean count.

Unfortunately, the Stacktrace in the logfile just states that there was a
CacheFullException, but does not tell us which bean caused that exception - see
for example the appended stacktrace. How can one find out for sure which bean
this applies to?

So, as a way to find that out, we looked into the BEA Console and listed the
Bean usage of the corresponding EJB module. (Deployments -> Applications
-> choose EAR -> choose EJB -> Monitoring -> Entity-EJBs) We there
realized that the "Beans in Use Current Count" is for some beans quite
high in comparison to what we would expect it to be - say 17000 for a bean with
only 9000 instances, and in another case 50000 for bean, whose instances are
only created, touched once a few seconds later and then never touched again.
This raises a few questions:

- What does "Beans In Use Current Count" exactly mean? What beans are
in the cache? Obviously it is not the count of beans in use by currently running
transactions: the JTA monitor does not show any inflight transactions. And there
are no transactions that use more than, say, a couple of dozen beans, anyway.

- Is it possible that the server does not release the beans from the cache after
completed transactions? If so: can it happen that it does not reuse them?

- Do you have any other ideas how to diagnose this problem?

Regards,

Björn


and here, a small part of the stacktrace:
de.telekom.gpp.ws.service.access.AccessServiceImpl -
handleException(CompanyRequest(1.0.0-ServiceControl(ANTK,testsessionid
/testrequestid):EntityId-345787a0-ec2c-11dc-a262-f2d3053a109c), <null>,
null)
java.rmi.RemoteException: EJB Exception: ; nested exception is:
        javax.ejb.TransactionRolledbackLocalException: Exception in ejbLoad:;
nested exception is: weblogic.ejb20.cache.CacheFullException: size=22581, targe
t000, incr=1
        at
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:186)