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

Shutdown of broker waiting for shared fileystem lock blocks

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 5.4.2
    • 5.6.0
    • Broker
    • None
    • Patch Available

    Description

      Shutting down a broker that has not completed startup due to waiting for a shared filesystem lock does not complete.

      Using an internal BrokerService() and it's stop() method is definitely impacted.

      The attached patch simply adds a check for "isStopped() || isStopping()" to the MessageDatabase lock loop.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tabish Timothy A. Bish
            artnaseef Arthur Naseef
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment