Recurring CacheFullException when creating new Entity Bean

Question

Normally I can create new instances of my Entity Bean just fine. However, at some point (whether it's after a rollback or not, I don't yet know), I get a CacheFullException when trying to create a new Entity Bean.
The CacheFullException exception shows a size that increments by one each time this error occurs. The reported size in the exception continually increases way past the max-beans-in-cache amount of 1000. Yet, the Administrator console reports the "Cached beans current count" as zero. So, the cache appears empty, yet every attempt to create a new entity bean fails with a CacheFullException!
I am using Weblogic Server 8.1 SP3, database concurrency strategy, BMP, and Oracle 9i. The Entity Bean's primary key class was generated by EJBGen (primary key is a java long).
Stopping and restarting the Weblogic server fixes the problem temporarily.
Any help would be greatly appreciated.
Jim

Answer 1

Yes, but if objects are equal they should have same
hashCode. If it is not happening, you have a problem.Yes, and equal objects do have the same hash code. Please see below for primary key class implementation as generated by EJBGen 2.16.
There can be a bug in reporting number of beans.OK, are you saying there is a bug that sometimes shows 0 beans in the cache when the cache is actually full? And even if the cache were full, all the beans would have to be involved in transactions for there not to be room for one more new bean in the cache. And I know that there are no other transactions going on, because this is an isolated system that only I am using. Again, Weblogic Server 8.1 SP3.
It is possible if your PKs don't implement
equals/hashCode correctly.They look correct to me. Here is the primary key class implementation as generated by EJBGen 2.16. The primary key is a java long, and I am using CMP (not BMP as I mistakenly reported earlier).
public class StatusPK implements Serializable {
public long statusID;
public StatusPK() {}
public StatusPK(long statusID) {
this.statusID = statusID;
private int m_hashCode = 0;
public int hashCode() {
if(0==m_hashCode) {
m_hashCode = ((int) statusID);
return m_hashCode;
public boolean equals(Object other) {
if(other==this) return true;
if(null==other) return false;
if(other.hashCode() != hashCode()) return false;
try {
StatusPK other2 = (StatusPK) other;
return (this.statusID==other2.statusID)
catch(ClassCastException ex) {
return false;
The only problem I see with this class is if the default constructor (no args) would be called, then the primary key and hashCode would always be zero. However, I'm assuming here that EJBGen knows what it is doing and that the default constructor is never actually used. In addition, I know that all of the beans in the database have valid primary keys, and they were created the same way that eventually continually fails later on.
Thanks...
jereitz