From 35a5a4a4ab8835005fb0f5d914f9f820707f894a Mon Sep 17 00:00:00 2001 From: Artem Bilan Date: Tue, 19 Jul 2016 12:29:21 -0400 Subject: [PATCH] Fix typos in the `delayer.adoc` --- src/reference/asciidoc/delayer.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/reference/asciidoc/delayer.adoc b/src/reference/asciidoc/delayer.adoc index e2efb2979b..51f3c6bd38 100644 --- a/src/reference/asciidoc/delayer.adoc +++ b/src/reference/asciidoc/delayer.adoc @@ -34,7 +34,7 @@ In the example above, the 3 second delay would only apply when the expression ev If you only want to apply a delay to Messages that have a valid result of the expression evaluation, then you can use a 'default-delay' of 0 (the default). For any Message that has a delay of 0 (or less), the Message will be sent immediately, on the calling Thread. -tTIP: The delay handler supports expression evaluation results that represent an interval in milliseconds (any Object whose `toString()` method produces a value that can be parsed into a Long) as well as `java.util.Date` instances representing an absolute time. +TIP: The delay handler supports expression evaluation results that represent an interval in milliseconds (any Object whose `toString()` method produces a value that can be parsed into a Long) as well as `java.util.Date` instances representing an absolute time. In the first case, the milliseconds will be counted from the current time (e.g. a value of 5000 would delay the Message for at least 5 seconds from the time it is received by the Delayer). With a Date instance, the Message will not be released until the time represented by that Date object. @@ -93,7 +93,7 @@ The `DelayHandler` persists delayed Messages into the Message Group in the provi (The 'groupId' is based on required 'id' attribute of `` element.) A delayed message is removed from the `MessageStore` by the scheduled task just before the `DelayHandler` sends the Message to the `output-channel`. If the provided `MessageStore` is persistent (e.g. `JdbcMessageStore`) it provides the ability to not lose Messages on the application shutdown. -After application startup, the`DelayHandler` reads Messages from its Message Group in the `MessageStore` and reschedules them with a delay based on the original arrival time of the Message (if the delay is numeric). +After application startup, the `DelayHandler` reads Messages from its Message Group in the `MessageStore` and reschedules them with a delay based on the original arrival time of the Message (if the delay is numeric). For messages where the delay header was a `Date`, that is used when rescheduling. If a delayed Message remained in the `MessageStore` more than its 'delay', it will be sent immediately after startup. @@ -119,7 +119,7 @@ A sample configuration of the `` may look like this: ---- -The `DelayHandler` can be exported as a JMX `MBean` with managed operations `getDelayedMessageCount` and `reschedulePersistedMessages`, which allows the rescheduling of delayed persisted Messages at runtime, for example, if the`TaskScheduler` has previously been stopped. +The `DelayHandler` can be exported as a JMX `MBean` with managed operations `getDelayedMessageCount` and `reschedulePersistedMessages`, which allows the rescheduling of delayed persisted Messages at runtime, for example, if the `TaskScheduler` has previously been stopped. These operations can be invoked via a `Control Bus` command: [source,java] ----