Following is what we are trying to achieve.
We want a big xml file to be staged in a database parallely in different vms. To achieve this, we are using the scalable spr
Found the issue that we were having.
The slave was including the spring batch job definition twice that caused the number of consumers to be registered twice for each slave. I think that we are missing some configuration to route messages back from the slave to the master when we have two partitions running concurrently on the slave correctly so at this point as long as we have one partition going to one slave (we are multithreading on the slave ) we are fine.