Glenn Renfro

In this case it was to allow task to utilize its own transaction manager seperate from those that may be provided by the user. More can be read about this...

Thank you @kewne for your issue and the thought that went into it. 1. In this case Spring Cloud Task needs to respect the transaction managers that are provided by...

After further investigation the upgrade to the latest Spring-Cloud-Deployer-Local caused the issue. The current deployer adds all environment variables to the command line args, when running from the command line....

We need to update the SimpleEnvironmentVariablesProvider to either set environment variables into the SPRING_APPLICATION_JSON. Or update the documentation to let the user's know that they should use SPRING_APPLICATION_JSON.

When PR https://github.com/spring-cloud/spring-cloud-task/pull/402 is merged this issue will be resolved. Refer to https://github.com/spring-cloud/spring-cloud-task/issues/401

@jvalkeal Also noticed when running this TestClass alone, there are no failures. Only when run with other classes. I noticed that TaskConfiguration is the only commonality between this test and...

SimpleSingleTaskAutoConfigurationWithDataSourceTests verifies that the Configuration for the singleInstanceTaskListener is working properly. (The singleInstanceTaskListener prevents a task from starting if another task with the same name is running. This is implemented...

What version of SqlServer and Task are you using?

Sorry for the delay in response. Please try Task 2.4.3.

I tried to reproduce this problem but was unable to do so. Can you provide a small sample that shows this behavior? Thanks!