jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting" <jukka.zitt...@gmail.com>
Subject Re: Working with JCR in highly concurrent applications
Date Fri, 22 Sep 2006 06:17:46 GMT

On 9/22/06, Alexandru Popescu <the.mindstorm.mailinglist@gmail.com> wrote:
> Thanks Yukka. That's what I have thought too, but I was looking more
> for technical arguments, so that I understand the real risk. Or at
> least a pointer to where to look for possible problems.
> I mean, if the access through the shared Session is read-only, what
> can go wrong? Have a node/property loaded 2 times? That's not so
> bad/risky (at least at first glance :-) ).

Hmm, I've never thought about it from that angle. There are some
internal caches that get modified even in read-only sessions. I don't
think those data structures are thread-safe, so you might end up
corrupting the internal state.


Jukka Zitting

Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development

View raw message