[
https://issues.apache.org/jira/browse/SLING-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding updated SLING-4981:
----------------------------------
Description:
I repeatedly observed a deadlock situation in an AEM 6.1 installation
(involving custom code).
The result, amongst others, is a blocked SCR Actor thread.
Hypothesis: I suspect that this can occur in situations where a scheduled Job
(A) has a reference to another SCR component (B) that is lazily initialized
(immediate=false) and itself registered via the whiteboard. If A is disabled
while B is being added by the Scheduler, this triggers deregistration of B as
well.
[~cziegeler] could you please take a look at the attached thread-dump? Several
subsequent thread-dumps showed no progress. I would appreciate your opinion on
this.
was:
I repeatedly observed a deadlock situation in an AEM 6.1 installation
(involving custom code).
The result, amongst others, is a blocked SCR Actor thread.
Hypothesis: I suspect that this can occur in situations where a scheduled Job
(A) has a reference to another SCR component (B) that is lazily initialized
(immediate=false) and itself registered via the whiteboard. If A is disabled
while B is being added by the Scheduler, this triggers deregistration of B as
well.
[~cziegeler] could you please take a look at the attached thread-dump? I would
appreciate your opinion on this.
> Deadlock involving Scheduler Whiteboard
> ---------------------------------------
>
> Key: SLING-4981
> URL: https://issues.apache.org/jira/browse/SLING-4981
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Scheduler 2.4.6
> Reporter: Julian Sedding
> Attachments: scheduler-scr-deadlock.log
>
>
> I repeatedly observed a deadlock situation in an AEM 6.1 installation
> (involving custom code).
> The result, amongst others, is a blocked SCR Actor thread.
> Hypothesis: I suspect that this can occur in situations where a scheduled Job
> (A) has a reference to another SCR component (B) that is lazily initialized
> (immediate=false) and itself registered via the whiteboard. If A is disabled
> while B is being added by the Scheduler, this triggers deregistration of B as
> well.
> [~cziegeler] could you please take a look at the attached thread-dump?
> Several subsequent thread-dumps showed no progress. I would appreciate your
> opinion on this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
