Yikes I made a big mistake here...
DELETE FROM BATCH_STEP_EXECUTION_CONTEXT ;
DELETE FROM BATCH_JOB_EXECUTION_CONTEXT ;
DELETE FROM BATCH_STEP_EXECUTION ;
DELETE FROM BATCH_JOB_EXECUTION ;...
Type: Posts; User: johnmmcparland; Keyword(s):
Yikes I made a big mistake here...
DELETE FROM BATCH_STEP_EXECUTION_CONTEXT ;
DELETE FROM BATCH_JOB_EXECUTION_CONTEXT ;
DELETE FROM BATCH_STEP_EXECUTION ;
DELETE FROM BATCH_JOB_EXECUTION ;...
At long last I figured this out.
I didn't have to change any of my Spring configuration from the first example (except if I wished to include the date/time parameter).
In fact what was wrong...
I created my own JobParametersIncrementer and used a JobOperator with my own main method rather than a JobLauncher & CommandLineRunner (I'd read I need to do this here)
But I'm no further...
Thanks for your reply Michael.
Here it is;
SEVERE: Job Terminated in error: PreparedStatementCallback; SQL [INSERT into BATCH_JOB_INSTANCE(JOB_INSTANCE_ID, JOB_NAME, JOB_KEY, VERSION)...
Within the Process part (ItemProcessor) you can make it do whatever you like.
Often what I do is create a class which requires a "service" bean and calls methods upon that. The "service" bean has...
I've used this with v2.1.7.RELEASE
DELETE FROM BATCH_STEP_EXECUTION_CONTEXT ;
DELETE FROM BATCH_JOB_EXECUTION_CONTEXT ;
DELETE FROM BATCH_STEP_EXECUTION ;
DELETE FROM BATCH_JOB_EXECUTION ;...
Hi,
I have defined a Spring Batch job which runs once just fine. However it is unable to run a second time due to a duplicate entry in the primary key for the JOB_INSTANCE_ID;
SEVERE: Job...