I want an "Updater" stateless session bean which updates an entity bean,
then obtains the new copy of the entity bean's fields (the database contains
triggers which alter some fields on the entity).
This means that the Entity Bean's update transaction must complete before I
read it again. The Entity Bean's transaction attribute is TX_MANDATORY. I
absolutely do not want TX_REQUIRES_NEW on any Entity Bean, so as to force
the front end to interact with Session Beans.
Thus, I need two transactions -- one to update the entity, the other to get
its updated field values. I've written an Updater session bean, with
transaction attribute TX_BEAN_MANAGED, which performs this:
///////
transaction = this.getSessionContext().getUserTransaction();
transaction.begin();
...method call on another session bean with TX_REQUIRED which actually
performs the update on the Entity
transaction.commit();
///////
The trouble is, I get an com.ibm.ejs.container.IsolationLevelChangeException
(I'm using VisualAge3.02EE)
on my EJB Server which forces the transaction to be rolled back every time.
All my beans throughout have their isolation level set to
TRANSACTION_SERIALIZABLE.
Any helpful advice is appreciated!
-Charles May
Charles May, Software Engineer
AFCO Credit Corp. - Pittsburgh Systems Group
A Mellon Financial Company
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
