Hi, I have the same problem with Oracle 8.1.7
I have a session facade and Jboss throws A TransactionRolledBackException and not the CreateException and my session bean dies...
And by the way... I'am just realizing something important : an EJB create is not always 'atomic' !
Imagine you have a method like :
Bean1Home.create(String id, String data, Bean2 bean2)
Bean2 has a relation to Bean1. You set it in the create method to enforce the API user to set the relation.
Due to EJB limitations, the relation cannot be built in ejbCreate but has to be set in ejbPostCreate.
Now, what happens if ejbCreate() works but ejbPostCreate fails ?? the create method is supposed to throw a CreateException (which seems not to be the case on JBoss 3.2 RC1) but what happens to the partial DB record ? I suppose that a rollback needs to be triggered to ensure DB integrity...
About the bug ... I also noticed that it only happens
when you set CMR in the ejbPostCreate() ... it works normally with a CMP field.