Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.17.0
-
Component/s: camel-core
-
Labels:None
-
Patch Info:Patch Available
-
Estimated Complexity:Unknown
Description
Not sure if this is a bug or just a documentation flaw (in fact I could not find documentation for it). Nevertheless, as a naive user, I kind of expected that the RejectedExecutionHandler of ThreadPoolRejectedPolicy.Abort would have similar semantics as Java's ThreadPoolExecutor.AbortPolicy. That is, I expected it to throw an Exception.
Currently (that is in the 2.15.2 release, and on the master branch in git) that is not the case. In fact, Abort seems to work exactly the same way as Discard.