Hi Milind,
> We are using a transactional data source. A declarative transaction > is started in the session bean ( we are using 'Required' transaction > attribute ). That sounds all right. > After first SQL statement an exception takes place. Though second > SQL statement is not executed but first SQL statement is committed Assuming that your database supports transactions it might be a problem with the exception. Only exceptions derived from RuntimeException (e.g. EJBException) force container managed transactions to be rolled back. We had similar problems with WLS 6.1 using setRollbackOnly() in case of a Checked Exception (that is, one that's not derived von RuntimeException). But we used entity beans together with session beans. Hope that helps. Please let us know, how you solved your problem! best regards, Phillip. --- Phillip Ghadir, [EMAIL PROTECTED] innoQ Deutschland GmbH, Harkortstrasse 21-23, D-40880 Ratingen, Germany Phone: +49 (2102) 77162-100 Mobile: +49 (170) 963 9704 Fax: +49 (2102) 77160-1 http://www.innoq.com/ http://iqgen.innoq.org/ http://www.mda-seminar.de/ -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr f�r 1 ct/ Min. surfen! =========================================================================== 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".
