[AMQ-3696] Slave broker cannot be stopped in a JDBC Master/Slave configuration within OSGi

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

Environment

ServiceMix 4.3

• Patch Info: Patch Available
• Assignee: Dejan Bosanac
• Reporter: metatech
• Created: 03/Feb/12 14:19
• Updated: 04/Sep/15 13:21
• Resolved: 19/Jul/12 13:26

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.

Issue Links

• requires: AMQ-3681 DatabaseLocker should first cancel locking SQL statement before closing the SQL connection