Issues in calling DAO from Sateless session bean

I have a stateless session bean which uses container managed transactions. I
had to call
a DAO in which I insert two records, from the session bean. If there is an
exception while inserting
second record in the DAO, I am facing the problem that the first record is
already commited
inspite of throwing the Exception.

I was able to have a workaround by calling setRollbackonly on the
transaction context. I am not sure
why this should be done. If the transactions are managed by container and I
am not calling commit
explicitly why should I call setRollbackonly.

Does anyone have any idea why this works this way?

Regards,
Koya Suresh



===========================================================================
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".