Class TimerScheduler
- java.lang.Object
- 
- org.apache.pekko.actor.TimerScheduler
 
- 
 public abstract class TimerScheduler extends java.lang.ObjectSupport for scheduledselfmessages in an actor. It is used by mixing in traitTimersin Scala or extendingAbstractActorWithTimersin Java.Timers are bound to the lifecycle of the actor that owns it, and thus are cancelled automatically when it is restarted or stopped. TimerScheduleris not thread-safe, i.e. it must only be used within the actor that owns it.
- 
- 
Constructor SummaryConstructors Constructor Description TimerScheduler()
 - 
Method SummaryAll Methods Instance Methods Abstract Methods Concrete Methods Deprecated Methods Modifier and Type Method Description abstract voidcancel(java.lang.Object key)Cancel a timer with a givenkey.abstract voidcancelAll()Cancel all timers.abstract booleanisTimerActive(java.lang.Object key)Check if a timer with a givenkeyis active.voidstartPeriodicTimer(java.lang.Object key, java.lang.Object msg, java.time.Duration interval)Deprecated.Use startTimerWithFixedDelay or startTimerAtFixedRate instead.abstract voidstartPeriodicTimer(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration interval)Deprecated.Use startTimerWithFixedDelay or startTimerAtFixedRate instead.voidstartSingleTimer(java.lang.Object key, java.lang.Object msg, java.time.Duration timeout)Start a timer that will sendmsgonce to theselfactor after the giventimeout.abstract voidstartSingleTimer(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration timeout)Start a timer that will sendmsgonce to theselfactor after the giventimeout.voidstartTimerAtFixedRate(java.lang.Object key, java.lang.Object msg, java.time.Duration interval)Java API: Schedules a message to be sent repeatedly to theselfactor with a given frequency.voidstartTimerAtFixedRate(java.lang.Object key, java.lang.Object msg, java.time.Duration initialDelay, java.time.Duration interval)Java API: Schedules a message to be sent repeatedly to theselfactor with a given frequency.abstract voidstartTimerAtFixedRate(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration interval)Scala API: Schedules a message to be sent repeatedly to theselfactor with a given frequency.abstract voidstartTimerAtFixedRate(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration initialDelay, scala.concurrent.duration.FiniteDuration interval)Scala API: Schedules a message to be sent repeatedly to theselfactor with a given frequency.voidstartTimerWithFixedDelay(java.lang.Object key, java.lang.Object msg, java.time.Duration delay)Java API: Schedules a message to be sent repeatedly to theselfactor with a fixeddelaybetween messages.voidstartTimerWithFixedDelay(java.lang.Object key, java.lang.Object msg, java.time.Duration initialDelay, java.time.Duration delay)Java API: Schedules a message to be sent repeatedly to theselfactor with a fixeddelaybetween messages after theinitialDelay.abstract voidstartTimerWithFixedDelay(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration delay)Scala API: Schedules a message to be sent repeatedly to theselfactor with a fixeddelaybetween messages.abstract voidstartTimerWithFixedDelay(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration initialDelay, scala.concurrent.duration.FiniteDuration delay)Scala API: Schedules a message to be sent repeatedly to theselfactor with a fixeddelaybetween messages after theinitialDelay.
 
- 
- 
- 
Method Detail- 
cancelpublic abstract void cancel(java.lang.Object key) Cancel a timer with a givenkey. If canceling a timer that was already canceled, or key never was used to start a timer this operation will do nothing.It is guaranteed that a message from a canceled timer, including its previous incarnation for the same key, will not be received by the actor, even though the message might already be enqueued in the mailbox when cancel is called. 
 - 
cancelAllpublic abstract void cancelAll() Cancel all timers.
 - 
isTimerActivepublic abstract boolean isTimerActive(java.lang.Object key) Check if a timer with a givenkeyis active.
 - 
startPeriodicTimerpublic abstract void startPeriodicTimer(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration interval)Deprecated.Use startTimerWithFixedDelay or startTimerAtFixedRate instead. This has the same semantics as startTimerAtFixedRate, but startTimerWithFixedDelay is often preferred. Since Akka 2.6.0.
 - 
startPeriodicTimerpublic final void startPeriodicTimer(java.lang.Object key, java.lang.Object msg, java.time.Duration interval)Deprecated.Use startTimerWithFixedDelay or startTimerAtFixedRate instead. This has the same semantics as startTimerAtFixedRate, but startTimerWithFixedDelay is often preferred. Since Akka 2.6.0.
 - 
startSingleTimerpublic abstract void startSingleTimer(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration timeout)Start a timer that will sendmsgonce to theselfactor after the giventimeout.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 - 
startSingleTimerpublic final void startSingleTimer(java.lang.Object key, java.lang.Object msg, java.time.Duration timeout)Start a timer that will sendmsgonce to theselfactor after the giventimeout.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 - 
startTimerAtFixedRatepublic abstract void startTimerAtFixedRate(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration interval)Scala API: Schedules a message to be sent repeatedly to theselfactor with a given frequency.It will compensate the delay for a subsequent message if the sending of previous message was delayed more than specified. In such cases, the actual message interval will differ from the interval passed to the method. If the execution is delayed longer than the interval, the subsequent message will be sent immediately after the prior one. This also has the consequence that after long garbage collection pauses or other reasons when the JVM was suspended all "missed" messages will be sent when the process wakes up again.In the long run, the frequency of messages will be exactly the reciprocal of the specified interval.Warning: startTimerAtFixedRatecan result in bursts of scheduled messages after long garbage collection pauses, which may in worst case cause undesired load on the system. ThereforestartTimerWithFixedDelayis often preferred.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 - 
startTimerAtFixedRatepublic abstract void startTimerAtFixedRate(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration initialDelay, scala.concurrent.duration.FiniteDuration interval)Scala API: Schedules a message to be sent repeatedly to theselfactor with a given frequency.It will compensate the delay for a subsequent message if the sending of previous message was delayed more than specified. In such cases, the actual message interval will differ from the interval passed to the method. If the execution is delayed longer than the interval, the subsequent message will be sent immediately after the prior one. This also has the consequence that after long garbage collection pauses or other reasons when the JVM was suspended all "missed" messages will be sent when the process wakes up again.In the long run, the frequency of messages will be exactly the reciprocal of the specified intervalafterinitialDelay.Warning: startTimerAtFixedRatecan result in bursts of scheduled messages after long garbage collection pauses, which may in worst case cause undesired load on the system. ThereforestartTimerWithFixedDelayis often preferred.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 - 
startTimerAtFixedRatepublic final void startTimerAtFixedRate(java.lang.Object key, java.lang.Object msg, java.time.Duration interval)Java API: Schedules a message to be sent repeatedly to theselfactor with a given frequency.It will compensate the delay for a subsequent message if the sending of previous message was delayed more than specified. In such cases, the actual message interval will differ from the interval passed to the method. If the execution is delayed longer than the interval, the subsequent message will be sent immediately after the prior one. This also has the consequence that after long garbage collection pauses or other reasons when the JVM was suspended all "missed" messages will be sent when the process wakes up again.In the long run, the frequency of messages will be exactly the reciprocal of the specified interval.Warning: startTimerAtFixedRatecan result in bursts of scheduled messages after long garbage collection pauses, which may in worst case cause undesired load on the system. ThereforestartTimerWithFixedDelayis often preferred.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 - 
startTimerAtFixedRatepublic final void startTimerAtFixedRate(java.lang.Object key, java.lang.Object msg, java.time.Duration initialDelay, java.time.Duration interval)Java API: Schedules a message to be sent repeatedly to theselfactor with a given frequency.It will compensate the delay for a subsequent message if the sending of previous message was delayed more than specified. In such cases, the actual message interval will differ from the interval passed to the method. If the execution is delayed longer than the interval, the subsequent message will be sent immediately after the prior one. This also has the consequence that after long garbage collection pauses or other reasons when the JVM was suspended all "missed" messages will be sent when the process wakes up again.In the long run, the frequency of messages will be exactly the reciprocal of the specified interval.Warning: startTimerAtFixedRatecan result in bursts of scheduled messages after long garbage collection pauses, which may in worst case cause undesired load on the system. ThereforestartTimerWithFixedDelayis often preferred.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 - 
startTimerWithFixedDelaypublic abstract void startTimerWithFixedDelay(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration delay)Scala API: Schedules a message to be sent repeatedly to theselfactor with a fixeddelaybetween messages.It will not compensate the delay between messages if scheduling is delayed longer than specified for some reason. The delay between sending of subsequent messages will always be (at least) the given delay.In the long run, the frequency of messages will generally be slightly lower than the reciprocal of the specified delay.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 - 
startTimerWithFixedDelaypublic abstract void startTimerWithFixedDelay(java.lang.Object key, java.lang.Object msg, scala.concurrent.duration.FiniteDuration initialDelay, scala.concurrent.duration.FiniteDuration delay)Scala API: Schedules a message to be sent repeatedly to theselfactor with a fixeddelaybetween messages after theinitialDelay.It will not compensate the delay between messages if scheduling is delayed longer than specified for some reason. The delay between sending of subsequent messages will always be (at least) the given delay.In the long run, the frequency of messages will generally be slightly lower than the reciprocal of the specified delay.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 - 
startTimerWithFixedDelaypublic final void startTimerWithFixedDelay(java.lang.Object key, java.lang.Object msg, java.time.Duration delay)Java API: Schedules a message to be sent repeatedly to theselfactor with a fixeddelaybetween messages.It will not compensate the delay between messages if scheduling is delayed longer than specified for some reason. The delay between sending of subsequent messages will always be (at least) the given delay.In the long run, the frequency of messages will generally be slightly lower than the reciprocal of the specified delay.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 - 
startTimerWithFixedDelaypublic final void startTimerWithFixedDelay(java.lang.Object key, java.lang.Object msg, java.time.Duration initialDelay, java.time.Duration delay)Java API: Schedules a message to be sent repeatedly to theselfactor with a fixeddelaybetween messages after theinitialDelay.It will not compensate the delay between messages if scheduling is delayed longer than specified for some reason. The delay between sending of subsequent messages will always be (at least) the given delay.In the long run, the frequency of messages will generally be slightly lower than the reciprocal of the specified delay.Each timer has a key and if a new timer with same key is started the previous is cancelled. It is guaranteed that a message from the previous timer is not received, even if it was already enqueued in the mailbox when the new timer was started. 
 
- 
 
-