Hi. I have verified with Oracle that there is a current and longstanding
bug in the Oracle DBMS, which may cause transactions with SERIALIZABLE
isolation level to silently fail. This affects EJBs as well as any other
transactional client.
The bug arises in transactions where a given row is inserted then updated
within a single transaction. The update may silently fail. This is a common
EJB scenario.
Tech support has told me that the bug (Oracle bug #440317) has been
repeatedly put off being fixed (since Jan '97) because of the scope of work
involved in fixing it.
If you might be affected by this bug, you should contact Oracle support about
Oracle bug #440317, and add your concern to the case. Only when there is a
critical mass of awareness and concern will Oracle feel justified in committing
the resources to this issue.
Thank you in advance if you speak up, and forgiveness requested for your time
if this is not of your concern.
PS: A SQL-PLUS script to demonstrate the bug is available on request.
Joe Weinstein at BEA, the home of WebLogic
--------------------------------------------------------------------------------
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web Application Server
Crossroads A-List Award: Rapid Application Development Tools for Java
Intelligent Enterprise RealWare: Best Application Using a Component Architecture
http://weblogic.beasys.com/press/awards/index.htm
===========================================================================
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".
