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

Elasticsearch and AMQP DefaultEventForwarder classes need @InOnly interface

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 18.0.0
    • 19.0.0
    • Eventd
    • Security Level: Default (Default Security Scheme)
    • None

    Description

      When testing the new Discovery code, I found that the DefaultDispatcher class used there doesn't send Camel message asynchronously unless the @Produce-annotated field has an interface that is annotated @InOnly.

      In the event forwarder classes, we reused the org.opennms.netmgt.events.api.EventForwarder interface for the fields. Because that is a core API interface that shouldn't need to rely on a Camel dependency, we should make a copy or subclass of the interface that resides inside the event forwarding projects that has an @InOnly annotation.

      Until this is done, event forwarding is probably synchronous within Eventd which could lead to performance problems.

      Attachments

        Activity

          People

            seth Seth Leger
            seth Seth Leger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: