+++ This bug was initially created as a clone of Bug #785026 +++ Description of problem: If event logging is enabled but native support is disabled, events do not get processed. A pure Java alternative should be provided in cases where native support is unavailable or the user should be warned that although event logging is enabled for a resource, it will not be active due to native support being disabled. Version-Release number of selected component (if applicable): 4.3 How reproducible: Always Steps to Reproduce: 1. Enable event logging for an AS resource or RHQ Agent 2. Confirm events are being logged 3. Restart agent with the --nonative command-line option Actual results: No events are logged once the agent is started with --nonative and the agent log contains no information indicating that event logging is failing Expected results: Event logging should continue to work Additional info: Ian's response from rhq-devel https://fedorahosted.org/pipermail/rhq-devel/2012-January/001434.html confirms this issue exists and suggests that it might be possible to implement a pure Java option. --- Additional comment from ian.springer on 2012-01-27 10:00:28 EST --- Raising the sev on this to medium. We really should be logging a warning. It would also be nice if we threw an exception in the plugins if a user tried to enable log events when native support is disabled in the Agent. But I think getting log events to work w/out SIGAR is low priority, since we support SIGAR on all the major platforms. --- Additional comment from mfoley on 2012-01-30 11:37:01 EST --- per 12/30/2012 BZ triage meeting mfoley, ccrouch, loleary, asantos we are splitting this BZ into 2 ... 1) we are reducing the scope of this BZ. providing customer feedback *is* the new reduced scope of this BZ ... and this is being targetted for 3.01. 2) i will be cloning a 2nd BZ as an RFE for the pure java alternative
Unsetting Target Release field and marking this as an Improvement