Issue Type: Feature Request Feature Request
Affects Versions: 0.5
Assignee: Unassigned
Components: component-rules
Created: 25/Jun/12 5:24 AM
Description:

Startup of SwitchYard 0.5 Beta1 shows the following:

080
05:17:06,844 INFO  [org.switchyard.component.common.rules.util.drools.ResourceChangeService] (MSC service thread 1-3) Starting resource change service...
05:17:06,873 INFO  [org.switchyard.component.common.rules.util.drools.LogSystemEventListener] (MSC service thread 1-3) ResourceChangeNotification created
05:17:06,876 INFO  [org.switchyard.component.common.rules.util.drools.LogSystemEventListener] (Thread-64) ResourceChangeNotification has started listening for ChangeSet publications
05:17:06,880 INFO  [org.switchyard.component.common.rules.util.drools.LogSystemEventListener] (MSC service thread 1-3) ResourceChangeScanner reconfigured with interval=60
05:17:06,881 INFO  [org.switchyard.component.common.rules.util.drools.LogSystemEventListener] (MSC service thread 1-3) ResourceChangeScanner created with default interval=60
05:17:06,889 INFO  [org.switchyard.component.common.rules.util.drools.LogSystemEventListener] (Thread-65) ResourceChangeNotification scanner has started
05:17:06,892 INFO  [org.switchyard.component.common.rules.util.drools.ResourceChangeService] (MSC service thread 1-3) Resource change service started.

Does any of this need to be in the log at INFO? Also, why is this happening at startup vs. on-demand when a rules or bpm service is deployed?
Fix Versions: 0.5
Project: SwitchYard
Priority: Major Major
Reporter: Keith Babo
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira