Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Logging not initialized but used on Drools Rule files.

Description

The files located on $OPENNMS_HOME/etc/examples/drools-engine.d/nodeParentRules/, to be more precise NodeParentRules.drl and drools-engine.xml are not properly initializing the logging engine which makes the rules unusable.

I was able to verify this behavior by just copy the files from the examples directory into opennms-correlation/drools-correlation-engine/src/test/opennms-home/etc/drools-engine.d/nodeParentRules/. The JUnit tests related with these files won't pass.

Actually, I think that the files we ship with OpenNMS must be identical to the files we verified through JUnit tests.

For the logging issue, we should at least comment the lines on the affected files for now, until we figure out how to properly initialize the logging engine with drools.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Jeff Gehlbach August 3, 2015 at 10:29 AM

This was not a problem with logger initialization at all, but a case of an undeclared global for the LOG bean in the rules files.

Seth Leger June 10, 2015 at 12:15 PM

Fixed by reverting back to println logging.

commit 1e6470b9523bfe1482673611524c09fa463356d3

Alejandro Galue June 2, 2015 at 5:16 PM

If the LOG entries are not removed, the example files cannot be used because they are going to break the correlation daemon.

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created May 27, 2015 at 11:59 AM
Updated August 3, 2015 at 10:29 AM
Resolved June 10, 2015 at 12:15 PM

Flag notifications