Overview

The previous sections discussed the flow for receiving messages from a message bus. The AepEngine also supports the ability for applications to inject message creating within the application's process. This can be useful for an application to schedule deferred work (from an event handler), or when an external thread would like to schedule work against an application (as only events dispatched from an AepEngine are permitted to interact with an application's state). 

Injecting Messages

The below code snippet demonstrates using injection to schedule MessageB to be dispatched to the application in the future.

Injection from an Event/Message Handler

Important: Injection of messages from an event handler does not result in the Message being added to the current transaction. Consequently, a failure of the engine prior to it being dispatched will result in the message being discarded. See HA Considerations below.

Delayed or Priority Injection

The value of the delay parameter is interpreted as follows:

• A value of 0 causes the message to be added to the end of the underlying engine's event multiplexer queue for immediate dispatch after already enqueued events.
• A positive value is interpreted in milliseconds and will cause the execution of the event to be scheduled no sooner than the delay period. When 2 events are scheduled by the same thread with a positive delay that results in the same scheduled execution time, then the events are executed in the order they were added. For example, if E1 is injected at time T with a delay of 2ms and E2 injected at time T + 1ms with a delay of 1ms, E2 will be scheduled after E1 (presuming a clock precision with a resolution of 1ms for System.currentTimeMillis()).
• A negative value is treated as a high priority dispatch and such messages are added to the beginning of the engine's event multiplexer queue. A lower delay represents a higher priority dispatch. When 2 events are scheduled with the same negative delay, the latter scheduled event will be executed after the former.
  NOTE: Priorities less than -1000 are reserved for platform use.

Behavior when not in HA Active Role

The message will only be injected on Started engines operating in the Primary role. Calls to inject are ignored on backup instances since it is expected that the injected message will be replicated from the primary. Calls made while an engine is replaying from a transaction log (e.g. State.Starting) are similarly ignored as those calls would interfere with the stream being replayed. An application that injects messages from an external source may call AepEngine.waitForMessagingToStart() to avoid an injected message being discarded while an engine is transitioning to a started, primary role. It is important to note that message injection is thus effectively a BestEffort operation because injections of messages that are in the event multiplexer queue at the time of failure will be lost. Reliable injection can be achieved via scheduleMessage(IRogMessage, int, com.neeve.aep.AepScheduleEvent.HAPolicy) though fault-tolerant scheduling incurs slightly higher overhead.

Message Pooling Considerations

The engine inject methods transfer ownership of the message to the platform. The method caller must not modify the message subsequent to this call. The platform will call dispose() on the message once it has been dispatched, so an application must call MessageView.acquire() if it will hold on to a (read-only) reference to the message.

Blocking vs. Non-Blocking Considerations

Care must be taken when considering whether to use using blocking or non-blocking injection. If the injecting thread is injecting to an engine multiplexer that may itself block on a resource held by the thread trying to inject, it can cause a deadlock. Conversely, using non-blocking dispatch can result in excessive memory growth, increased latency, and fairness issues. Therefore, if the injecting thread is drawing events from an external source, blocking dispatch is generally the right choice, but if injection is being performed from a message handler, non-blocking should be used.