JSR 352 -为什么包括在<skippable exception -classes>中的异常会停止作业？

Question

我正在尝试使用JSR 352创建一个简单的批处理应用程序，并使用Websphere 17.0.0.2。在进入异常处理之前，一切似乎都很正常。我假设job.xml中“可跳-异常-类”节点中指定的应用程序引发的异常将被忽略/跳过，并允许作业继续下一项/步骤。

当从注入bean (通过@Inject)调用其方法时抛出异常时，我遇到的问题就会发生。作业只在抛出异常的当前项/步骤上停止。

奇怪的是，每当我手动/显式抛出完全相同的异常，比方说RecordNotFoundException，作业就会继续进行，这正是我所期望的。只有当从注入的bean触发异常时，才会出现问题。我在异常类中添加了@ApplicationException，所以异常包装/解包装已经就位。

我是不是遗漏了什么？这是Websphere with的窃听器吗？

编辑:添加简化代码

SampleSharedLibrary -来自其他项目/jar的依赖关系

package sample;

import javax.ejb.ApplicationException;
import javax.ejb.Stateless;

@Stateless
public class SampleSharedLibrary {

    public String someMethod(String object) {
        String result = null;

        if(object != null) {
            result = "OK";
        } else {
            throw new MyException();
        }

        return result;
    }

    @ApplicationException(rollback = true)
    public static class MyException extends RuntimeException {
        public MyException() {}
    }
}

BatchExample应用

SampleWriter进口sample.SampleSharedLibrary；

import javax.batch.api.chunk.AbstractItemWriter;
import javax.enterprise.context.Dependent;
import javax.inject.Inject;
import javax.inject.Named;
import java.util.List;

@Dependent
@Named("SampleWriter")
public class SampleWriter extends AbstractItemWriter{

    @Inject
    SampleSharedLibrary sharedLibrary;

    public void writeItems(List<Object> list) throws Exception {
        for(Object item : list) {
            sharedLibrary.someMethod(item.toString());
        }
    }
}

SampleReader

import javax.batch.api.chunk.AbstractItemReader;
import javax.enterprise.context.Dependent;
import javax.inject.Named;
import java.io.Serializable;

@Dependent
@Named("SampleReader")
public class SampleReader extends AbstractItemReader {

    String[] sample;
    int index;
    @Override
    public void open(Serializable checkpoint) throws Exception {
        sample = new String[]{"S1", null, "S3"};
        index = 0;
    }

    public Object readItem() throws Exception {
        Object item = null;

        if(index < sample.length) {
            item = sample[index];
            index++;
        }

        return item;
    }
}

job.xml

<job id="myJob" xmlns="http://xmlns.jcp.org/xml/ns/javaee" version="1.0">
    <step id="myStep" >
        <chunk item-count="1" skip-limit="50">
            <reader ref="SampleReader"/>
            <writer ref="SampleWriter"/>
            <skippable-exception-classes>
                <include class="java.lang.Exception"/>
                <include class="sample.SampleSharedLibrary$MyException"/>
            </skippable-exception-classes>
        </chunk>
    </step>
</job>

至于server.xml，添加的配置不多，但我启用了以下特性: cdi-1.2、ejbLite-3.2、jaxs-2.0、jpa-2.0、jsf-2.2、managedBeans-1.0、servlet-3.1、localConnector-1.0、批处理-1.0和json-1.0。

当遇到实际应用程序的错误时，我会得到如下所示的日志(必须将一些值更改为星号)：

[02-11-17 21:38:12:323 CST] 000000d1 com.ibm.ws.logging.internal.impl.IncidentImpl                I FFDC1015I: An FFDC Incident has been created: "*******.**********.*******.batchflows.service.writer.ErrorWhileUpdating: *******.**********.*******.infrastructure.*****.commands.OurCommand$RecordNotFound: recordId=31AA69FAE017D21F com.ibm.jbatch.container.controller.impl.ChunkStepControllerImpl 485" at ffdc_17.11.02_21.38.12.0.log
[02-11-17 21:38:12:352 CST] 000000d1 com.ibm.ws.logging.internal.impl.IncidentImpl                I FFDC1015I: An FFDC Incident has been created: "com.ibm.jbatch.container.exception.BatchContainerRuntimeException: *******.**********.*******.batchflows.service.writer.ErrorWhileUpdating: *******.**********.*******.infrastructure.*****.commands.OurCommand$RecordNotFound: recordId=31AA69FAE017D21F com.ibm.jbatch.container.controller.impl.ChunkStepControllerImpl 1041" at ffdc_17.11.02_21.38.12.1.log
[02-11-17 21:38:12:363 CST] 000000d1 com.ibm.ws.logging.internal.impl.IncidentImpl                I FFDC1015I: An FFDC Incident has been created: "javax.transaction.RollbackException com.ibm.jbatch.container.transaction.impl.JTAUserTransactionAdapter 107" at ffdc_17.11.02_21.38.12.2.log
[02-11-17 21:38:12:385 CST] 000000d1 com.ibm.ws.logging.internal.impl.IncidentImpl                I FFDC1015I: An FFDC Incident has been created: "com.ibm.jbatch.container.exception.TransactionManagementException: javax.transaction.RollbackException com.ibm.jbatch.container.controller.impl.ChunkStepControllerImpl 680" at ffdc_17.11.02_21.38.12.3.log

Answer 1

即使批处理容器跳过给定的异常，EJB容器仍然可以回滚批块事务。

将作业XML配置为跳过给定的异常只会阻止批处理容器标记块事务以供回滚。它不会阻止其他人将事务标记为回滚。

这意味着EJB容器本身可以回滚事务。因此，在您的情况下，您需要使用：

@ApplicationException(rollback = false)
public static class MyException extends RuntimeException {

或者，在预注释风格中，您需要使用检查异常而不是未检查的异常，以防止EJB容器回滚事务。