[OAK-1703] Improve warning logged on concurrent Session access

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.2, 1.1.0
• Component/s: jcr
• Labels: concurrency
• Assignee: Michael Dürig
• Reporter: Michael Dürig
• Created: 09/Apr/14 07:26
• Updated: 01/Oct/14 13:11
• Resolved: 07/Jul/14 12:51

Description

OAK-1601 introduced warnings that are logged when a session is accessed concurrently from different threads. The modalities however differ from those of Jackrabbit 2. The message

Attempt to perform "sessionOperation" while another thread is concurrently writing to "session". Blocking until the other thread is finished using this session. Please review your code to avoid concurrent use of a session.

is logged for the current thread

• if the current threads attempts a write operation while another thread already executes a write operation in Jackrabbit 2,
• if the current thread attempts a write operation while another thread already executes any operation.

We should make these warnings identical to those of Jackrabbit 2.