簡體   English   中英

Spring Batch Step流程功能是否存在錯誤?

[英]Is there a bug in Spring Batch Step flow function?

在下面的代碼中,當StepA失敗時,僅應執行StepB和StepC,但實際上發生的是所有3個步驟都已執行! 我想根據某個步驟是否通過來拆分一個春季批處理作業。 我知道還有其他方法可以通過使用JobDecider,設置一些作業參數等來實現,但是我想知道我在這里做錯了嗎?

@Configuration
@EnableBatchProcessing
public class JobConfig {

    @Autowired
    private JobBuilderFactory jobBuilderFactory;

    @Autowired
    private StepBuilderFactory stepBuilderFactory;

    @Bean
    public PlatformTransactionManager transactionManager() {
        return new ResourcelessTransactionManager();
    }

    @Bean
    public JobRepository jobRepository() {
        try {
            return new MapJobRepositoryFactoryBean(transactionManager())
                    .getJobRepository();
        } catch (Exception e) {
            return null;
        }
    }

    @Bean
    public JobLauncher jobLauncher() {
        final SimpleJobLauncher launcher = new SimpleJobLauncher();
        launcher.setJobRepository(jobRepository());
        return launcher;
    }

    @Bean
    public Job job() {
        return jobBuilderFactory.get("job").
                flow(stepA()).on("FAILED").to(stepC()).next(stepD()).
                from(stepA()).on("*").to(stepB()).next(stepC()).end().build();
    }

    @Bean
    public Step stepA() {
        return stepBuilderFactory.get("stepA")
                .tasklet(new RandomFailTasket("stepA")).build();
    }

    @Bean
    public Step stepB() {
        return stepBuilderFactory.get("stepB")
                .tasklet(new PrintTextTasklet("stepB")).build();
    }

    @Bean
    public Step stepC() {
        return stepBuilderFactory.get("stepC")
                .tasklet(new PrintTextTasklet("stepC")).build();
    }

    @Bean
    public Step stepD() {
        return stepBuilderFactory.get("stepD")
                .tasklet(new PrintTextTasklet("stepD")).build();
    }

    @SuppressWarnings("resource")
    public static void main(String[] args) {
        // create spring application context
        final ApplicationContext appContext = new AnnotationConfigApplicationContext(
                JobConfig.class);
        // get the job config bean (i.e this bean)
        final JobConfig jobConfig = appContext.getBean(JobConfig.class);
        // get the job launcher
        JobLauncher launcher = jobConfig.jobLauncher();
        try {
            // launch the job
            JobExecution execution = launcher.run(jobConfig.job(), new JobParameters());
            System.out.println(execution.getJobInstance().toString());
        } catch (JobExecutionAlreadyRunningException e) {
            e.printStackTrace();
        } catch (JobRestartException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        } catch (JobInstanceAlreadyCompleteException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        } catch (JobParametersInvalidException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        }
    }

}

步驟A:是一個失敗的虛擬作業,即它拋出一些異常公共類RandomFailTask​​et擴展了PrintTextTasklet {

    public RandomFailTasket(String text) {
        super(text);
    }

    public RepeatStatus execute(StepContribution arg0, ChunkContext arg1)
            throws Exception {

        if (Math.random() < 0.5){
            throw new Exception("fail");
        }
        return RepeatStatus.FINISHED;
    }

}

StepB,StepC和StepD也是虛擬的Tasklet:公共類PrintTextTasklet實現Tasklet {

    private final String text;

    public PrintTextTasklet(String text){
        this.text = text;
    }


    public RepeatStatus execute(StepContribution arg0, ChunkContext arg1)
            throws Exception {
        System.out.println(text);
        return RepeatStatus.FINISHED;
    }

}

需要看看您正在使用的xml結構。

嘗試使用Step偵聽器-然后在after step方法中可以檢查Step狀態,然后可以實現邏輯以調用或不調用下一步

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM