Simplest recovery use case
When you observe the following restrictions the correlator’s recovery behavior is straightforward:
All monitors are persistent. The correlator contains no Java and no chunks.
There are no implementations of
onBeginRecovery() or
onConcludeRecovery() actions.
EPL code that adheres to these restrictions appears to behave as if it is running in a completely reliable and fault tolerant system. The downside is that while the correlator is down, incoming or outgoing events are dropped. If you implement a "retransmit until acknowledge" protocol then the correlator can have a large number of events (and retransmits) to process when it restarts, depending on how long it is down.
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.