Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-6250

MultiKahaDBTransactionStore should have null protection in close

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 5.9.1, 5.13.2
    • 5.13.3, 5.14.0
    • KahaDB
    • None

    Description

      When utilizing the MultiKahaDBPersistenceAdapter and there is a failure during broker startup, (depending on when the startup failure occurs) a secondary NullPointerException can be generated from MultiKahaDBTransactionStore.close. this happens if the transaction store is closed when it has not yet been opened. the problem is that the close method does not check the journal for null before closing.

      Attachments

        Activity

          People

            cshannon Christopher L. Shannon
            jahlborn james
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: