0 Replies Latest reply on Oct 12, 2016 5:28 AM by Mr. T

    Envers + JTA + Oracle

    Mr. T Newbie

      Hello everyone,

      It appears i have the following problem...



      1. Entity annotated with @Audited

      2. Oracle 10g

      3. JTA

      4. Wildfly 10


      To replicate the problem i simply rename one column of the entity audit table, fill the entity with some values and commit.


      Envers will throw an error because it doesn't recognize the renamed column, obviously, and throw a rollback exception.

      The problem is that the transaction is committed anyway. The data is saved and no audit is generated because the audit itself gave an error.

      This only seems to happen with Oracle. In a test environment with H2 he effectively rolls back the transaction and doesn't save the data.


      Any ideas...?