Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.1.2
-
Fix Version/s: None
-
Component/s: Core: Exception Handling
-
Labels:None
-
User impact:Very High
-
Similar Issues:None
Description
The call to logException(e) in method handleException(Exception e) from org.mule.exception.DefaultSystemExceptionStrategy class is not protected against exceptions.
Thus, if an exception arise :
- no exception is logged (the source one or the new one) ;
- the retry policy isn't applied because the end of handleException method is skipped.
We do face this issue because of this other bug : MULE-6261 : logException raise a MissingResourceException (while looking for CoreMessages.exceptionStackIs() ) and thus we don't have any retry policy working.
Activity
Alejandro Sequeira
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Priority | To be reviewed [ 6 ] | Critical [ 2 ] |
Alejandro Sequeira
made changes -
| Priority | Critical [ 2 ] | Major [ 3 ] |
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
- Repository mule on http://foo.bar/ failed: Error in remote call to 'FishEye 0 (http://foo.bar/)' (http://foo.bar) [AbstractRestCommand{path='/rest-service-fe/changeset-v1/listChangesets/', params={expand=changesets[-21:-1].revisions[0:29], comment=MULE-6283, p4JobFixed=MULE-6283, rep=mule}, methodType=GET}] : java.net.UnknownHostException: foo.bar