ActiveMQ is configured in a Master/Slave configuration with an Oracle database :
When the slave node is stopping, "activemq-broker" stays forever in the "Stopping" state.
This is because the locking SQL statement cannot be interrupted by just closing the JDBC connection. It is also needed to "cancel" the SQL statement.
Here is a patch to DefaultDatabaseLocker which makes it compatible with Oracle.