EJB CMP remove create cache issue? DuplicateKeyException

Question

EJB CMP remove create cache issue? DuplicateKeyException
Hi I have an EJB 2.1 application using CMP. Most things work fine. But if I in a transaction tries to remove a bean and create a new one with the same primary key I get a DuplicateKeyException:
2007-11-16 09:25:31,963 ERROR [RMICallHandler-6] AdminGroupData_ConcreteSubClass147 - Error adding AccessRules:
javax.ejb.DuplicateKeyException: Exception [EJB - 10007]: Exception creating bean of type [AccessRulesData]. Bean already exists.
at oracle.toplink.internal.ejb.cmp.EJBExceptionFactory.duplicateKeyException(EJBExceptionFactory.java:195)
I suspect that the remove call only removes from the cache (until commit), but that the create call checks the database or something?
My code is simple like the following:
AdminPreferencesDataLocal apdata1 = adminpreferenceshome.findByPrimaryKey(certificatefingerprint);
adminpreferenceshome.remove(certificatefingerprint);
adminpreferenceshome.create(certificatefingerprint,newadminpreference);
Is there some configuration I can set in toplink-ejb-jar.xml to fix this?
I use OC4j 10.1.3.3
Cheers,
Tomas

Answer 1

The bean.remove() was executed but the sql DELETE was executed to the database as the result, oc4j manages all sql statements and they are optimized to commit to the database in batch at once when the transaction commit. Oc4j ejb container is smart and preventing you from creating the same entity cached in the transaction because the sql delete was not really committed to the database when the create is called.
My guess is that the reason it works with IBM WAS was because it issued sql for each remove/create call right away instead of doing them in batch as oc4j, or your WAS remove then create were called in separate transactions.