You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/07/03 19:26:50 UTC

[jira] Assigned: (SLING-1581) Concurrent session access in event handlers

     [ https://issues.apache.org/jira/browse/SLING-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler reassigned SLING-1581:
---------------------------------------

    Assignee: Carsten Ziegeler

> Concurrent session access in event handlers
> -------------------------------------------
>
>                 Key: SLING-1581
>                 URL: https://issues.apache.org/jira/browse/SLING-1581
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Extensions Event 2.3.0
>            Reporter: Jukka Zitting
>            Assignee: Carsten Ziegeler
>             Fix For: Extensions Event 2.4.0
>
>         Attachments: SLING-1581.patch
>
>
> I have a deadlock scenario caused by one thread calling AbstractRepositoryEventHandler.stopWriterSession() while another thread is attempting to lock a node using the same session in TimedJobHandler.runInBackground().
> There's already a writeLock object in TimedJobHandler that's apparently designed to protect against concurrent use of the writer session, but that protection doesn't seem to cover the stopWriterSession() method in the base class.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.