Contexts and correlator determinism
Creating one or more contexts makes the correlator non-deterministic. In other words, injecting the same monitor can product different results if the monitor contains statements that spawn to contexts.
For example, suppose an application creates two contexts, spawns to each of them, and each context runs code that calls integer.getUnique(). The assignment of unique integers to contexts is not deterministic; if you re-run the code, each context might receive an integer that is different from the integer it received during the previous run. Other behavior that can be non-deterministic in a parallel processing application includes the following:
The assignment of particular IDs to particular contexts
The order in which contexts emit events
The order in which contexts enqueue events to other contexts
The order in which contexts spawn to other contexts
See also
About replay logs and parallel processing in
Deploying and Managing Apama Applications.
Copyright © 2013
Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.