Annotation Interface Archive
ArchivePollingContainer.
Template can be provided using EventTemplate marked on a general
method that returns the template.
- Author:
- Itai Frenkel
- See Also:
-
Optional Element Summary
Optional ElementsModifier and TypeOptional ElementDescriptionThe name of the bean that is theArchiveOperationHandlerthis container will use.booleanSet whether this container will start once instantiated.intintSpecify the number of concurrent consumers to create.The name of the bean that is theGigaSpacethis container will use.intSpecify the maximum number of concurrent consumers to create.booleanIf set totruewill perform snapshot operation on the provided template before invoking registering as an event listener.longSet the timeout to use for receive calls, in milliseconds.longbooleanThe value may indicate a suggestion for a logical component name, to be turned into a Spring bean in case of an autodetected component.
-
Element Details
-
value
String valueThe value may indicate a suggestion for a logical component name, to be turned into a Spring bean in case of an autodetected component.- Returns:
- the suggested component name, if any
- Default:
- ""
-
gigaSpace
String gigaSpaceThe name of the bean that is theGigaSpacethis container will use.Note, this is optional. If there is only one
GigaSpacedefined in the application context, it will be used.- Default:
- ""
-
concurrentConsumers
int concurrentConsumersSpecify the number of concurrent consumers to create. Default is 1.Specifying a higher value for this setting will increase the standard level of scheduled concurrent consumers at runtime: This is effectively the minimum number of concurrent consumers which will be scheduled at any given time. This is a static setting; for dynamic scaling, consider specifying the "maxConcurrentConsumers" setting instead.
Raising the number of concurrent consumers is recommended in order to scale the consumption of events. However, note that any ordering guarantees are lost once multiple consumers are registered. In general, stick with 1 consumer for low-volume events.
- Default:
- 1
-
maxConcurrentConsumers
int maxConcurrentConsumersSpecify the maximum number of concurrent consumers to create. Default is 1.If this setting is higher than "concurrentConsumers", the listener container will dynamically schedule new consumers at runtime, provided that enough incoming messages are encountered. Once the load goes down again, the number of consumers will be reduced to the standard level ("concurrentConsumers") again.
Raising the number of concurrent consumers is recommended in order to scale the consumption of events. However, note that any ordering guarantees are lost once multiple consumers are registered. In general, stick with 1 consumer for low-volume events.
- Default:
- 1
-
receiveTimeout
long receiveTimeoutSet the timeout to use for receive calls, in milliseconds. The default is 60000 ms, that is, 1 minute.NOTE: This value needs to be smaller than the transaction timeout used by the transaction manager (in the appropriate unit, of course).
- Default:
- 60000L
-
performSnapshot
boolean performSnapshotIf set totruewill perform snapshot operation on the provided template before invoking registering as an event listener.- See Also:
- Default:
- true
-
autoStart
boolean autoStartSet whether this container will start once instantiated.Default is
true. Set tofalsein order for this container to be started usingAbstractEventListenerContainer.start().- Default:
- true
-
recoveryInterval
long recoveryInterval- Default:
- 5000L
-
batchSize
int batchSize- Default:
- 50
-
archiveHandler
String archiveHandlerThe name of the bean that is theArchiveOperationHandlerthis container will use.Note, this is optional. If there is only one
ArchiveOperationHandlerdefined in the application context, it will be used.- Default:
- ""
-
useFifoGrouping
boolean useFifoGrouping- Default:
- false
-