Out of curiosity, I looked up the discussion that Carsten was referring to [0]. Along the same lines as Justin's comments, not a supported feature, so if you care about the integrity of your repository, you probably shouldn't do it.
[0] http://jackrabbit.510166.n4.nabble.com/jr3-Synchronized-sessions-td1567869.ht ml#a1569247 -----Original Message----- From: justinedel...@gmail.com [mailto:justinedel...@gmail.com] On Behalf Of Justin Edelson Sent: Thursday, September 29, 2011 11:21 AM To: users@sling.apache.org Subject: Re: Evenhandlers, Session and Threadsafety On Thu, Sep 29, 2011 at 8:13 AM, Carsten Ziegeler <cziege...@apache.org> wrote: > 2011/9/29 Bertrand Delacretaz <bdelacre...@apache.org>: >> On Thu, Sep 29, 2011 at 3:16 PM, Carsten Ziegeler <cziege...@apache.org> wrote: >>> I wouldn't rely on concurrent reads with the same session. In rare >>> cases this can lead to problems! >> >> Do you have more info about that? >> (not disputing, just curious) > > Not that much :) But with heavy concurrent reads I ran into a problem > from time to time and I asked the Jackrabbit developers about it. And > they confirmed that this "might happen" and they discourage all > concurrent usage. This was roughly eight months ago FWIW, I think the bigger point is that concurrent usage of a session isn't a supported use case. It *might* work some of the time, but if it doesn't, you shouldn't be surprised. Regards, Justin
