Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-642

amsessiondb does not recover from db errors and can break the MQ

    XMLWordPrintable

    Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • Express8, Snapshot9, Snapshot9.5, Snapshot9.5.1, Snapshot9.5.2_RC1, Snapshot9.5.2, 9.5.3_RC1
    • 9.5.3, 10.0.0-EA
    • session
    • Rank:
      1|hzn7p3:
    • Sprint 3

      Description

      If the DB crashes/disk full then amsessiondb treats this as an MQ issue. It does not disconnect from the queues, but sits and waits for the MQ to fix itself. If the problem is DB related, the DB may never fix itself and amsessiondb will continue to be connected to the broker.

      Still being connected to the broker means the messages in the topics build up (as the amsessiondb is connect but not processing messages due to the db failure), this will lead to the brokers filling up and MQ dying.

        Attachments

          Activity

            People

            steve Steve Ferris
            steve Steve Ferris
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: