Skip to:

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

Drools correlation engine do not always respond to targeted reloadDaemonConfig events

Description

Steps to reproduce:

1. Begin with a fresh OpenNMS install
2. Enable the Correlator daemon in service-configuration.xml
3. Extract the file micro-repro-pack-5675.tar.bz2 (attached to this issue) into /opt/opennms
4. Start OpenNMS
5. Begin tail-following /var/log/opennms/DroolsCorrelationEngine-ticket5675Rules_0.log in one terminal
6. In a second terminal, run: send-event.pl uei.opennms.org/internal/reloadDaemonConfig -p 'daemonName DroolsCorrelationEngine-ticket5675Rules_0' repeatedly with a few seconds' delay between repetitions

Expected result: Log messages about engine reload in tail-follow for each event sent

Actual result: Log messages about engine reload only for every fifth event (totally consistent across about a dozen tries in my experience)

Environment

See https://mynms.opennms.com/Ticket/Display.html?id=5675

Acceptance / Success Criteria

None

Attachments

1

Lucidchart Diagrams

Activity

Show:

Jesse White July 24, 2018 at 4:50 PM

Jesse White July 24, 2018 at 4:49 PM

Thanks for making this one easy to reproduce .

I tracked the problem down to unnecessary refreshing of the event handlers.

Fixed

Details

Assignee

Reporter

Labels

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created July 10, 2018 at 6:37 PM
Updated July 26, 2018 at 7:02 PM
Resolved July 26, 2018 at 7:02 PM