Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-1583

Primary key violation on JMS_TRANSACTIONS

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBossAS-4.0.2 Final
    • JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.2RC1
    • JMS (JBossMQ)
    • None

      The calculation of the next transaction id in jms recovery is done in the wrong place.
      It should determine the next transaction id before it rolls back incomplete adds
      otherwise it will get the next transaction id wrong which could produce
      a primary key constraint violation on the JMS_TRANSACTIONS table.

          1.
          		 JMS_TRANSACTIONS constraint violation is not completely fixed Sub-task Closed Major Clebert Suconic

              adrian.brock Adrian Brock (Inactive)
              adrian.brock Adrian Brock (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: