Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
The consequence of this is that if the framework throws a FlowFileAccessException, for example, the Processor is catching that and then routing to failure, when the framework should be able to catch it and roll back the ProcessSession. Specifically, we are seeing this because on of the content repository containers ran out of disk space and files were then routed to 'failure'. Instead, the session should have been rolled back and the FlowFile processed again.