batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] [Created] (BATCHEE-88) rollback fails if the connection already got closed by the container
Date Fri, 15 Jan 2016 08:38:39 GMT
Mark Struberg created BATCHEE-88:

             Summary: rollback fails if the connection already got closed by the container
                 Key: BATCHEE-88
             Project: BatchEE
          Issue Type: Bug
          Components: jbatch-core
    Affects Versions: 0.3-incubating
            Reporter: Mark Struberg
            Assignee: Mark Struberg
             Fix For: 0.4-incubating

We get the following Exception in some cases. Happens if our Oracle closes the connection
alltogether after a constraint problem in the db.

2016-01-15 09:16:29,805 [@Asynchronous myapp-batches - 1] noSessionActive noUserId ERROR controller.BaseStepController
No transaction associated with current thread
java.lang.IllegalStateException: No transaction associated with current thread
        at org.apache.geronimo.transaction.manager.TransactionManagerImpl.setRollbackOnly(
        at org.apache.openejb.core.CoreUserTransaction.setRollbackOnly(
        at org.apache.batchee.container.impl.controller.chunk.ChunkStepController.rollback(
        at org.apache.batchee.container.impl.controller.chunk.ChunkStepController.invokeChunk(
        at org.apache.batchee.container.impl.controller.chunk.ChunkStepController.invokeCoreStep(
        at org.apache.batchee.container.impl.controller.BaseStepController.execute(
        at org.apache.batchee.container.impl.controller.ExecutionTransitioner.doExecutionLoop(
        at org.apache.batchee.container.impl.controller.JobThreadRootController.originateExecutionOnThread(

Any rollback exception should get catched away and the execution should continue normally

Any thoughts?

This message was sent by Atlassian JIRA

View raw message