Search:

I think this is an issue with the 2.1.3 release of Spring Batch.

I am using just a SimpleJobLauncher and the RunIdIncrementer, starting my jobs with the CommandLineJobRunner.

For my jobs, I may...

I am running Spring Batch 2.1.3 and I'm not getting good results from this.

I use the RunIdIncrementer to increment the runId automatically because most of the times I will run my job will the...

This issue has been resolved by upgrading to Spring 3.0.4 and Spring Batch 2.1.3.

thanks

file: is required in front of the parameter to get it to run correctly on Windows. without "file:" in front of the parameter then I get an org.springframework.batch.item.ItemStreamException. ...

I'm including a job log as I think it shows that the parameters are picked up correctly from the initiation of the job. It's just the reference to the #{jobParameters[]} that is failing. In this...

Yeah, I've validated and actually hard coded the classpath in the job to ensure it is the same. The only difference is it works running on Windows and does not on AIX.

what I meant by sent in as text is that when I specify this in the job xml:

<property name="parmEvent" value="#{jobParameters['event']}" />

Then in my program in the setParmEvent() method I get...

I have a job running fine when executed with CommandLineJobRunner on Windows. When I move this same job to an AIX platform and attempt to execute it through the CommandLineJobRunner, the...

This thread poses the exact questions I am trying to answer. Everything makes sense except that I am unable to stop a running job gracefully.

So for example to start my job from the command line...

thanks for the suggestion. it works very nicely.

I have a need to put together a job that will read from a database txn table, then edit each record against rules data collected from other database tables, then write out 1 or 2 records to the same...