4 Replies Latest reply on Feb 12, 2010 1:57 PM by user617110

    RowInconsistentException ignored by committing twice?

    187369
      I've encountered unwanted behavior of an ADF application, that can be reproduced simply with the BC4J tester application.
      The following scenario uses a simple application module on the DEPT table in the default HR-schema of Oracle XE.
      1) the application module locking mode is set to optimistic
      2) start 2 instances of the BC4J test app and scroll both to the same DEPT-record
      3) in the first test app: change the DepartmentName, press Enter and commit
      4) in the second test app: change the DepartmentName, press Enter and commit -> a RowInconsistentException is thrown correctly
      5) commit again (in the second test app): no RowInconsistentException is thrown and the changes are committed to the database!

      My question: is this correct behavior? I expected that committing would keep throwing the same exception (forcing the user to do a manual rollback or something like that).

      Many thanks.