batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (BATCHEE-44) Rollback should not swallow Exceptions
Date Wed, 09 Jul 2014 11:43:05 GMT


Hudson commented on BATCHEE-44:

SUCCESS: Integrated in batchee #531 (See [])
BATCHEE-44 exceptions during rollback must not hide the real problem exceptions (struberg:
rev cd766e03270258133248a985940dc6c092805a4f)
* jbatch/src/main/java/org/apache/batchee/container/services/persistence/jpa/
* jbatch/src/main/java/org/apache/batchee/container/services/persistence/
* jbatch/src/main/java/org/apache/batchee/container/services/persistence/jpa/provider/

> Rollback should not swallow Exceptions
> --------------------------------------
>                 Key: BATCHEE-44
>                 URL:
>             Project: BatchEE
>          Issue Type: Bug
>            Reporter: Mark Struberg
>             Fix For: 0.2-incubating
> If an Exception occurs in a batch, the PersitenceManager will rollback the currently
active transaction. 
> The problem arises if the Exception was caused by a database problem which implicitly
did already close the Connection to the database. In this case the rollback itself will fail
and cause an Exception as well. This causes us to only show the Exception caused by the rollback
but miss the actually important _real_ cause of the problem - the original Exception

This message was sent by Atlassian JIRA

View raw message