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.
Carsten Ziegeler 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.