Ever wonder why it takes a while to get your first batch of log file events... During component start plugins that support event sources create the logfile event pollers for enabled event sources. Unfortunately the poller creation is blocked because it is trying to use to the eventManager to access Sigar. This is because the initial component start takes place during container initialization, which holds a write lock and does not yet allow access to the managers. This results in a 60 second timeout, waiting for the lock. Which in turn (quietly) fails the component start. Eventually the component will be started again, when the pc for any reason tries to interact with the resource container. But the interrupted component start and poller creation is not good, and can potentially introduce issues depending on how well the plugin (and our poller code) is written.
commit d1a4410a78bfbed7baa8b65b71abea0315a3fea0 lazily access sigar on the first polling, which happens after container initialization. Test Notes Perhaps not super-easy to test but with debug logging on the agent and and an enabled event source (enable the built in event source for the RHQ Server resource) you should see no related messages of any severity for the component startup (at agent startup time). Also, the log event generation should work as expected, generating an event for each server log entry (assuming the default settings)
*** Bug 782796 has been marked as a duplicate of this bug. ***
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.