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
  3. JBAS-2056

JMS_TRANSACTIONS constraint violation is not completely fixed

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • JBossAS-4.0.3 Final
    • JBossAS-4.0.2 Final, JBossAS-4.0.3RC1
    • JMS (JBossMQ)
    • None
    • Compatibility/Configuration

    Description

      The fix for the constraint violation on JMS_TRANSACTIONS in JBAS-1583 does not always solve the problem.

      The problem could still occur if recovery completes succesfully but then JBoss crashes immediately.
      In this case, the original problem will still occur on subsequent recovery attempts.

      The recovery algorithm needs to be fixed to cater for repeat recovery attempts.
      i.e. It should select the maximum transaction id from both JMS_MESSAGES and JMS_TRANSACTIONS

      SELECT_MAX_TX = SELECT MAX(TXID) FROM (SELECT MAX(TXID) FROM JMS_TRANSACTIONS UNION SELECT MAX(TXID) FROM JMS_MESSAGES)

      Additonally, the root cause of the problem is that JMS_TRANSACTIONS should really be cleared
      DELETE FROM JMS_TRANSACTIONS
      when recovery is successful.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBAS-2261 DELETE_ALL_TX sql in the PersistenceManager.java should be configurable in the same was as the other sql statements.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBAS-2425 You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT MAX(TXID) AS TXID FROM JMS_TRANSACTIONS UNION SELECT MAX)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBAS-2424 JMS PersistenceManager: ...Could not resolve uncommited transactions....java.sql.SQLException: Every derived table must have its own alias

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              adrian.brock Adrian Brock (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: