I am trying to launch a job in Spring Batch 2, and I need to pass some information in the job parameters, but I do not want it to count for the uniqueness of the job instance. For example, I’d want these two sets of parameters to be considered unique:
file=/my/file/path,session=1234
file=/my/file/path,session=5678
The idea is that there will be two different servers trying to start the same job, but with different sessions attached to them. I need that session number in both cases. Any ideas?
Thanks!
So, if ‘file’ is the only attribute that’s supposed to be unique and ‘session’ is used by downstream code, then your problem matches almost exactly what I had. I had a JMSCorrelationId that i needed to store in the execution context for later use and I didn’t want it to play into the job parameters’ uniqueness. Per Dave Syer, this really wasn’t possible, so I took the route of creating the job with the parameters (not the ‘session’ in your case), and then adding the ‘session’ attribute to the execution context before anything actually runs.
This gave me access to ‘session’ downstream but it was not in the job parameters so it didn’t affect uniqueness.
References
https://jira.springsource.org/browse/BATCH-1412
http://forum.springsource.org/showthread.php?104440-Non-Identity-Job-Parameters&highlight=
You’ll see from this forum that there’s no good way to do it (per Dave Syer), but I wrote my own launcher based on the SimpleJobLauncher (in fact I delegate to the SimpleLauncher if a non-overloaded method is called) that has an overloaded method for starting a job that takes a callback interface that allows contribution of parameters to the execution context while not being ‘true’ job parameters. You could do something very similar.
I think the applicable LOC for you is right here:
jobExecution = jobRepository.createJobExecution(job.getName(),
jobParameters);
which is where, after execution context creatin, the execution context is added to. Hopefully this helps you in your implementation.