[
https://issues.apache.org/jira/browse/OAK-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig reopened OAK-1703:
--------------------------------
Reopening for 1.0.2: I think we should merge this to the 1.0 branch as the
wrong messages are confusing and do not help much for finding out who is
concurrently accessing the current session.
> Improve warning logged on concurrent Session access
> ---------------------------------------------------
>
> Key: OAK-1703
> URL: https://issues.apache.org/jira/browse/OAK-1703
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: concurrency
> Fix For: 1.0.2, 1.1
>
>
> 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
> {code}
> 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.
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
