Spring integration's DefaultLockRepository requires a TransactionManager.
However it assumes that only one is available. Since task can have more than one, we are allowed to tell SI which one to use
update db2 'between' logic to be exclusive
Signed-off-by: Ryan DCruz <rd@enfuse.io>
use .acceptLicense() instead of the classpath file
checkstyle
add test to verify a result set that's smaller than requested page size
cleanup
resolves TASK-782
Updated PR to resolve issue when no task tables exist
Updated PR based on review comments.
This does not include updated tests.
This resolves a problem where task would fail because the incrementer selection occured before the tables were created.
Added unit test for SqlServerSequenceIncrementer
updated based on code review
This commit now validates that the value passed via a PageRequest to
sort the results by is a valid value.
Resolves#739
Fixed to allow for all letter cases
Ensure that Task's org.springframework.cloud.task.configurationorg.springframework.cloud.task.configuration.MetricsAutoConfiguration is configured Before org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration (that in turn is configured Before the CompositeMeterRegistryAutoConfiguration).
Resolves#691
Before this commit, Spring Cloud Task did not correctly configure the
provided PlatformTransactionManager with the TaskRepository. This
commit addressis this bug.
Resolves#652
Polished PR on Merge
In short the Oracle CHAR type is blank padded to the end of the field. So we were not getting an exact match on queries when looking for the LOCK_KEY or CLIENT_ID
- New dependencies
- micrometer-core
- java-cfenv - required by the CF tags configuration.
- Add TaskMetrics configuration that installs two Meters (Timer and LongTaskTimer) that produce the following time-series:
- spring.cloud.task - shows task duration (updated only after the task has completed).
- spring.cloud.task.active - provides run time information about the non-completed tasks.
Both meters are started at TaskExecutionListener#onTaskStartup() and ended at onTaskEnd() or onTaskFailure().
- Add common Task tags assigned to all time-series produced by the Task (not only the s.c.task and s.c.task.active). This allows to analyze CPU, Memory and other measurements grouped by task/execution ids.
- Add Cloud Found tags - Activated only for CF target platform.
Resolves#608
Updated to spring-cloud-build 2.2.0.BUILD-SNAPSHOT
Updated Tests to support the changes in the latest H2 database
Must use "-ifNotExists", when using the H2 TCP Server
- Deployer core/local uses 2.0.0.BUILD-SNAPSHOT
- Use pring-cloud-deployer-dependencies bom
- Remove ResourceLoadingAutoConfiguration as that is now in
deployer itself with a way to configure loaders.
- spring-cloud-task-core now depends on spring-cloud-deployer-autoconfigure.
- Rest of deployer modules like support/maven are still defined in deps
as those are optional in spring-cloud-deployer-autoconfigure.
