Spring Batch挂起，没有状态更新

Question

昨晚大约6:00 pm，我启动了春季批处理工作（包括16个步骤）。 由于这是第一次运行，所以我希望它需要几个小时才能完成，并在今天早上完成。 但是，第一步是在读取和写入大约100万条记录后，该工作挂起。 我已经建立了一种机制，可以根据作业状态在作业失败时重新启动作业。 然而，

• BATCH_JOB_EXECUTION表中的作业状态显示为status =“ STARTED”，退出代码为“ UNKNOWN”
• BATCH_STEP_EXECUTION中的步骤状态显示状态=“ STARTED”，退出代码=“ EXECUTING”

在这种情况下，如何优雅地终止作业，以便可以重新启动它？ 那是处理这种情况的最佳方法吗？

我是否缺少任何配置属性？ 我应该设置任何其他属性吗？ 我的数据源配置如下：

<bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource">
            <property name="driverClassName" value="com.informix.jdbc.IfxDriver"/>
            <property name="url" value="<DBURL>" />
            <property name="username" value="<USERID>"  />
            <property name="password" value="<PASSWORD>" />
            <property name="initialSize" value="25" />
            <property name="maxIdle" value="15" /> <!-- maxIdle..The maximum number of connections that should be kept in the pool at all times. Idle connections are checked periodically (if enabled) and connections that have been idle for longer than minEvictableIdleTimeMillis are released. See also testWhileIdle. -->
            <property name="minIdle" value="5" /><!-- minIdle...The minimum number of established connections that should be kept in the pool at all times. The connection pool can shrink below this number if validation queries fail. The default value is derived from initialSize. -->
            <property name="maxActive" value="20" /> <!-- maxActive..The maximum number of active connections that can be allocated from this pool at the same time, or negative for no limit. -->
            <property name="maxWait" value="3000" /> <!-- maxWait..The maximum milliseconds a pool with no available connections will wait for a connection to be returned before throwing an exception, or -1 to wait indefinitely. -->
            <property name="removeAbandonedTimeout" value="2700" /> <!--removeAbandonedTimeout..Setting 15 minuts. Timeout in seconds before an abandoned connection can be removed. The value should be set to the longest running query your applications might have. -->
            <property name="logAbandoned" value="true" /> <!--logAbandoned.. Set to true to log stack traces for application code that abandons a Connection. Logging an abandoned Connection adds overhead for every Connection open because a stack trace has to be generated. -->
            <property name="idleConnectionTestPeriod" value="300" />    Test all connections in the pool every 5 minutes using the preferredTestQuery above -->
    </bean>

    <bean id="readerdataSource" class="org.apache.commons.dbcp.BasicDataSource">
            <property name="driverClassName" value="com.informix.jdbc.IfxDriver"/>
            <property name="url" value="<DBURL>" />
            <property name="username" value="<USERID>"  />
            <property name="password" value="<PASSWORD>" />
            <property name="defaultReadOnly" value="true" />
            <property name="initialSize" value="25" />
            <property name="maxIdle" value="15" /> <!-- maxIdle..The maximum number of connections that should be kept in the pool at all times. Idle connections are checked periodically (if enabled) and connections that have been idle for longer than minEvictableIdleTimeMillis are released. See also testWhileIdle. -->
            <property name="minIdle" value="5" /><!-- minIdle...The minimum number of established connections that should be kept in the pool at all times. The connection pool can shrink below this number if validation queries fail. The default value is derived from initialSize. -->
            <property name="maxActive" value="20" /> <!-- maxActive..The maximum number of active connections that can be allocated from this pool at the same time, or negative for no limit. -->
            <property name="maxWait" value="3000" /> <!-- maxWait..The maximum milliseconds a pool with no available connections will wait for a connection to be returned before throwing an exception, or -1 to wait indefinitely. -->
            <property name="removeAbandonedTimeout" value="2700" /> <!--removeAbandonedTimeout..Setting 15 minuts. Timeout in seconds before an abandoned connection can be removed. The value should be set to the longest running query your applications might have. -->
            <property name="logAbandoned" value="true" /> <!--logAbandoned.. Set to true to log stack traces for application code that abandons a Connection. Logging an abandoned Connection adds overhead for every Connection open because a stack trace has to be generated. -->
            <property name="defaultTransactionIsolation" value="1"/>
    </bean>