R – Spring Batch resourceless JobRepository

jakarta-eespring-batch

I'm using Spring Batch for a system that does a lot of batch operations.
I'm using SimpleJobRepository with in memory DAOs.
I would like to know if there is a way to avoid using a JobRepository? something similar to the resourceless transaction manager?
The reason i'm asking is that the system should run constantly without restarting and i have some concerns about the memory it will be consuming.
I know i can use a database based JobRepositry, but frankly, I really don't need one at all.

If there is no way to do so i will appreciate it if someone can reassure me about the memory consumption problem.

Thanks.

Best Answer

You must use job repository as it holds info about the job context. the solution for your case is - make your job repository with scope="prototype" this will cerate a new in-memory dao (map implementation) for each job, and thus no memory problem. the overhead of creating new instance each time is meaningless in terms of batch jobs.

Related Solutions

How to we share data between the different steps of a Job in Spring Batch

the job repository is used indirectly for passing data between steps (Jean-Philippe is right that the best way to do that is to put data into the StepExecutionContext and then use the verbosely named ExecutionContextPromotionListener to promote the step execution context keys to the JobExecutionContext.

It's helpful to note that there is a listener for promoting JobParameter keys to a StepExecutionContext as well (the even more verbosely named JobParameterExecutionContextCopyListener); you will find that you use these a lot if your job steps aren't completely independent of one another.

Otherwise you're left passing data between steps using even more elaborate schemes, like JMS queues or (heaven forbid) hard-coded file locations.

As to the size of data that is passed in the context, I would also suggest that you keep it small (but I haven't any specifics on the

Why is default isolation level of every method (of a spring batch job) for a spring integration and batch transaction set to SERIALIZABLE

It's SERIALIZABLE by default to prevent the same job instance being executed concurrently on 2 or more boxes. You can relax it if this is not a concern for you.

http://static.springsource.org/spring-batch/reference/html/configureJob.html#txConfigForJobRepository

The

isolation-level-for-create

attribute controls the propagation for create* and getLastJobExecution* methods

Best Answer

Related Solutions

How to we share data between the different steps of a Job in Spring Batch

Why is default isolation level of every method (of a spring batch job) for a spring integration and batch transaction set to SERIALIZABLE

Related Topic