Is there any way to ensure message order?

[ColleenFarrell]

We would like to use an input to GeoEvent processor that may not always send messages (a status message) in order. For example, an Open status may be sent a few seconds before a New status.  Currently I don't see a way to configure any of the current inputs for a situation like this.  Would a future input like Receive Feature JSON from ActiveMQ be able to do this?

It looks like ActiveMQ has a resequencer that could do what we want.(?)

Thanks.

[RyanElliott]

There is likely to be a connector released in the near future that supports ActiveMQ.  This could be used to resequence the messages.  However, the internal processing of GeoEvents in the GeoEvent Processor happens in multiple parallel processing threads.  Depending on how fast these different threads run, the GeoEvents could come out of the GeoEventProcessor in a different order than they went in.  This doesn't usually happen, but it is possible.

[ColleenFarrell]

Thanks for responding Ryan.

I think the capability that I am looking for is the Resequencer in Apache Camel, http://camel.apache.org/resequencer.html.

I was just wondering if the ActiveMQ connector would have this as a configuration option.