[BATCHEE-44] Rollback should not swallow Exceptions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.2-incubating
• Assignee: Mark Struberg
• Reporter: Mark Struberg
• Created: 09/Jul/14 09:52
• Updated: 07/Dec/15 22:40
• Resolved: 09/Jul/14 11:47

Description

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