Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-10257

Drools correlation engine do not always respond to targeted reloadDaemonConfig events

    XMLWordPrintable

Details

    • Horizon - July 11th 2018, Horizon - July 18th 2018, Horizon - July 25th 2018

    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)

      Attachments

        Activity

          People

            j-white Jesse White
            jeffg Jeff Gehlbach
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.