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

Slave broker cannot be stopped in a JDBC Master/Slave configuration within OSGi

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.4.2
    • Fix Version/s: 5.7.0
    • Component/s: Broker
    • Labels:
      None
    • Environment:

      ServiceMix 4.3

    • Patch Info:
      Patch Available

      Description

      A Blueprint container cannot be stopped while it is in the state "Creating" because both operations are synchronized in BlueprintContainerImpl.
      The impact is that a slave broker cannot be stopped. Fortunately, before the broker itself is stopped, first the OSGi services are unregistered, which calls the configured OSGi unregistration listeners.
      This patch provides a class which is a OSGi service unregistration listener, to allow to stop the database locker, while it is blocked in the "Creating" state.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dejanb Dejan Bosanac
                Reporter:
                metatech metatech
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1h
                  1h
                  Remaining:
                  Remaining Estimate - 1h
                  1h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified