0 Replies Latest reply on Nov 13, 2002 11:03 AM by jean

    commit-option C broken in 3.0.4

    jean Newbie

      Hi jboss gurus,
      commit-option C feature seems to be broken in jboss 3.0.4 release.
      My configuration : jboss 3.0.4 / MySQL / Redhat 7.2

      I've set the commit option to 'C' in standardjboss.xml because we are running several applications on the same database, so we don't want our entity beans to be cached as data is likely to change without using Jboss.

      I'm calling two function in a session bean.
      - The first flush several records in few tables, using "direct" SQL calls (better in that particular case than using entity remove() for performance because a lot of record are deleted).
      - The other creates records in the same table using entity beans.

      In jboss 3.0.3 : no problem.
      Running the same code in 3.0.4 :

      TransactionRolledbackException, causedBy:
      java.lang.IllegalStateException: INSERTING AN ALREADY EXISTING BEAN, ID = 24/1/24-5175-55/1

      Looking in database shows no record for that key, so the exception should not occurs. Seems that Jboss didn't see that my records were previously deleted, but that should not occurs with commit-option C, or I'm missing something ?
      Please help !