[CAMEL-15557] Multicast parallel processing with timeout: Stream Cache file not deleted if CachedOutputStream created before timeout and writing to CachedOutputStream happens after timeout

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.25.2, 3.4.3
• Fix Version/s: 3.4.4, 3.6.0, 2.25.3
• Component/s: camel-core
• Patch Info: Patch Available
• Estimated Complexity: Unknown
• Flags: Patch
• Assignee: Unassigned
• Reporter: Franz Forsthofer
• Created: 20/Sep/20 10:54
• Updated: 22/Sep/20 03:35
• Resolved: 21/Sep/20 04:39

Description

If you have a route with a Multicast with parallel processing and a timeout and a sub-route in the multicast which is creating an OutputStreamCache before the timeout and is writing to the OutputStreamCache after the timeout then the created file is never deleted from the file system.

 

Similar situation as described in https://issues.apache.org/jira/browse/CAMEL-15532. The difference to https://issues.apache.org/jira/browse/CAMEL-15532 is that the OutputStreamCache is created before the timeout; in CAMEL-15532 the OutputStreamCache was created after the timeout and also the writing to the OutputStreamCache happened after the timeout.

With our current concept to determine the UnitOfWork which removes via the onDone event the created file, we can only determine the described situation and throw an exception. See provided patch.

Issue Links

• links to: GitHub Pull Request #4260
• links to: GitHub Pull Request #4261
• links to: GitHub Pull Request #4262