task-executor | Task Executor in Golang | Job Scheduling library

I have the following task executor which is used to run a 10s sleep time tasklet with partitions:

I read data from a Q and pass to executor channel to process. No the transaction scope with main thread will not work. How can i can create a transaction from executor channel which has multiple direct channels downstream. Here is the config

I have a multithreading project where I read a message from a queue and pass it to spring integration to process it. Each messages goes though diff channel end up storing in DB and sending to downstream Qs.

I have requirement where i need to pass message to multiple channels asyc. To make my flow asyc i am using all executor channel. But for some reason flow is still sequential. i can seen diff thread as i configured in task executor but in sequence. Here is the configuration I am using

What would be the equivalent of the following outbound channel adapter configuration in spring boot? Assuming the messageChannel, taskExecutor, and synchronizationFactory are defined.

I have a spring boot web application and I want to upload details from CSV files through a batch process. Files can be upload from any location and I want to restrict the process 3 jobs at a time. if already in process of 3 files, we have to give that information to UI as, "Throttle limit is being reached. Try after some time". How Could I achieve this? My current flow.xml is with master slave approach

I am new to Spring batch and implementing a spring batch job where it has to pull huge data set from DB and write to file. Below is the sample job config which is working as expected for me.

I have a flow that starts with a poller and hands off the message to several async flows downstream using task-executors to execute in parallel for a given dataset. A downstream aggregator completes the flow and notifies the poller that the flow is complete.

I would like to track every execution of the poller by using MDC so that the logs can be mapped to a particular execution of the flow.

I started by adding MDC to the poller thread (using Advice), however with this approach there could be a couple of issues:

1. How do I stamp the MDC on the executor thread when the async hand off happens?
2. Since executor uses a a thread pool, do I need to clear the MDC before the thread returns to the pool? Will there be any side effects?

Another approach would be to add MDC to the Message header and set it manually on the new thread during the async handoff. How to do that? For example, if I turn on the debug logs, the MDC should be stamped right from the beginning of the new thread execution and not from the point where my logic starts in the service activator. How to set this on the task-executor thread (and probably also remove before returning to the pool) using XML configuration? Something like an MdcAwareThreadPoolExecutor seen here. Also, I would not want the MDC logic to be spread across all the async handoff endpoints, may be there is some generic way to configure it?

Is there a better way to achieve this? Any known solutions?

I have a flow that uses a pub/sub channel based gateway with 2 subscribers to send message to 2 SQS queues. In between I have chain to do message transformation. An aggregator is used to summarize the report of every gateway invocation. Happy path works fine, but when my transformer throws error I get this message Reply message received but the receiving thread has already received a reply and the aggregator gets invoked but future.get in the Runner never returns. Sample Config and code to test is as follows:

Config