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

["Jukka Zitting (JIRA)" <ji...@apache.org>]

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

Jukka Zitting updated SLING-1581:
---------------------------------

    Attachment: SLING-1581.patch

The proposed patch moves the writeLock object to the base class and uses it to synchronize more of the potentially concurrent session accesses.

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