Multiple instances of a partitioned spring batch job

Question

I have a Spring batch partitioned job. The job is always started with a unique set of parameters so always a new job.

My remoting fabric is JMS with request/response queues configured for communication between the masters and slaves.

One instance of this partitioned job processes files in a given folder. Master step gets the file names from the folder and submits the file names to the slaves; each slave instance processes one of the files.

Job works fine.

Recently, I started to execute multiple instances (completely separate JVMs) of this job to process files from multiple folders. So I essentially have multiple master steps running but the same set of slaves.

Randomly; I notice the following behavior sometimes - the slaves will finish their work but the master keeps spinning thinking the slaves are still doing something. The step status will show successful in the job repo but at the job level the status is STARTING with an exit code of UNKNOWN.

All masters share the set of request/response queues; one queue for requests and one for responses.

Is this a supported configuration? Can you have multiple master steps sharing the same set of queues running concurrently? Because of the behavior above I'm thinking the responses back from the workers are going to the incorrect master.

question from:https://stackoverflow.com/questions/65949185/multiple-instances-of-a-partitioned-spring-batch-job

Answer 1

Waitting for answers