Stopping one QuartzComponent stops all
--------------------------------------
Key: SM-735
URL: https://issues.apache.org/activemq/browse/SM-735
Project: ServiceMix
Issue Type: Bug
Components: servicemix-components
Affects Versions: 3.0
Reporter: Hrvoje Simic
Stopping a specific QuartzComponent (e.g. via JMX console) puts its scheduler
on standby. Since (by default) all QuartzComponents in a container use the
same, default scheduler, this causes _all_ of them to stop triggering events.
This is surprising for an administrator.
Perhaps the QuartzComponent could be rewritten to create its own scheduler on
initialization, or to pause only its own triggers instead of the entire
scheduler?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
