[
https://issues.apache.org/jira/browse/SLING-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh updated SLING-12661:
------------------------------
Description:
In case of excessive recursive calls, a huge stack of potential origins is
generated (see SLING-12478).
Make sure to use the last 500 messages of the RequestProgressTracker in the
analysis of potential origins and put them into the log message, avoiding huge
strings that may run into OOM errors.
was:
In case of excessive recursive calls, a huge stack of potential origins is
generated (see related SLING Jira ticket).
Make sure to use the last 500 messages of the RequestProgressTracker in the
analysis of potential origins and put them into the log message, avoiding huge
strings that may run into OOM errors.
> Potential origins of violations to the RequestDispatcher include API may run
> into OOM error on excessive recursions
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-12661
> URL: https://issues.apache.org/jira/browse/SLING-12661
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Remo Liechti
> Assignee: Remo Liechti
> Priority: Minor
> Fix For: Engine 2.16.0
>
>
> In case of excessive recursive calls, a huge stack of potential origins is
> generated (see SLING-12478).
> Make sure to use the last 500 messages of the RequestProgressTracker in the
> analysis of potential origins and put them into the log message, avoiding
> huge strings that may run into OOM errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
