Potential memory leak

For the REST connector failed jobs with multiple tasks consumed extensive amounts of memory resulting in OutOfMemory issues. The issue is resolved by the addition of the errorResponseFilter parameter. Enabling it overrides the default behavior during error occurrance, when the whole response is logged. Instead, it provides JsonPaths to properties which should be extracted from the response body.

JsonPaths should be enclosed withing the # sign. Multiple JsonPaths can be provided with the # separating them, for example:

errorResponsesFilter=#$.userName#$.roleAndCompany[*].notificationMessages.personId[*].message#

INC-268655