[
https://issues.apache.org/jira/browse/SLING-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-1040.
-----------------------------------
Resolution: Fixed
Fix Version/s: Commons Scheduler 2.0.6
The synchronization was way to aggressive and has been introduced by SLING-984;
I'Ve cleaned it up now to a minimum and also fixed some other minor issues in
revision: 792809
> Too much synchronization in QuartzScheduler?
> --------------------------------------------
>
> Key: SLING-1040
> URL: https://issues.apache.org/jira/browse/SLING-1040
> Project: Sling
> Issue Type: Bug
> Affects Versions: Commons Scheduler 2.0.4
> Reporter: Bertrand Delacretaz
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Commons Scheduler 2.0.6
>
> Attachments: deadlock-trace.txt
>
>
> In one of my jcrinstall tests I got a deadlock when jcrinstall tried to stop
> the org.apache.sling.commons.scheduler bundle while it was being started by
> the Felix ComponentActorThread.
> I'll attach the deadlock stack trace - wondering if some of the synchronized
> sections in QuartzScheduler could be removed, to avoid such issues.
> That might be a jcrinstall/Felix problem as well: stopping a bundle while it
> is being activated doesn't sound right, but I'm not sure how to prevent this,
> as the ComponentActorThread actions run asynchronously.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
