On 10.04.2014, at 01:44, Michael Dürig mdue...@apache.org wrote:
So when 2 threads use the same session for read operations, then you
get another warning (concurrent access)?
Right but only at debug level.
If the threads are synchronized, so one finishes its session
operations, then the
On 10.4.14 2:24 , Alexander Klimetschek wrote:
On 09.04.2014, at 07:15, Michael Dürig mdue...@apache.org wrote:
On 9.4.14 4:12 , Rob Ryan wrote:
It would be appropriate to change the warning to warn about
concurrent reads as well. That would help highlight performance
risks.
There is such
On 9.4.14 3:20 , Alexander Klimetschek wrote:
if I get this warning below, does another thread is concurrently
writing mean that the other threads is using session WRITE methods?
The message is actually misleading if not wrong. This warning is issued
if *this* thread does a write operation
On 9.4.14 4:55 , Rob Ryan wrote:
I can't comment to the exact meaning of the warning, but I can say
the impact of reading from multiple threads with one session is a
significant concern in itself given the current implementation of
Oak. Under high throughput conditions the lock contention
: Re: Session concurrency warning
On 9.4.14 3:20 , Alexander Klimetschek wrote:
if I get this warning below, does another thread is concurrently
writing mean that the other threads is using session WRITE methods?
The message is actually misleading if not wrong. This warning is issued
I can't comment to the exact meaning of the warning, but I can say the impact
of reading from multiple threads with one session is a significant concern in
itself given the current implementation of Oak. Under high throughput
conditions the lock contention quickly becomes a significant
