[SLING-1581] Concurrent session access in event handlers

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Event 2.3.0
• Fix Version/s: Event 2.4.0
• Component/s: Extensions
• Assignee: Carsten Ziegeler
• Reporter: Jukka Zitting
• Created: 02/Jul/10 13:33
• Updated: 06/Sep/10 14:02
• Resolved: 05/Jul/10 14:59

Description

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.