jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shaun Barriball" <sbarr...@yahoo.co.uk>
Subject RE: Profiling shows Session management to be a hotspot - session pooling etc
Date Thu, 29 Mar 2007 07:38:16 GMT
Hi all,
Yesterday we modified our 'view' web application to use a shared global
Session rather than Session per request pattern based on (appreciated)
feedback from the list. The result was a large increase in performance but
we are now seeing the following exception thrown periodically:

Caused by: javax.jcr.InvalidItemStateException:
el}styleClass: the item does not exist anym

.....which implies that the session is getting out of date with changes made
by the 'editor' web application. We're using a mdoel 2 deployment.

Is there anything we could be doing wrong in our code for this to occur or
is using a shared session a not viable?


-----Original Message-----
From: Jukka Zitting [mailto:jukka.zitting@gmail.com] 
Sent: 27 March 2007 14:45
To: users@jackrabbit.apache.org
Subject: Re: Profiling shows Session management to be a hotspot - session
pooling etc


On 3/27/07, David Nuescheler <david.nuescheler@gmail.com> wrote:
> the only issue that i am aware of with respect to concurrent read 
> operations on a shared session is during shutdown under certain special
> generally an application should be able to concurrently read from the 
> same session

Note that while this is currently true in Jackrabbit, it might not be true
in some other JCR implementation or in a future Jackrabbit release. We might
for example want to introduce some session-level read cache that would not
be thread-safe.

I would recommend using a thread pool instead of accessing a single session
from multiple threads.


Jukka Zitting

All New Yahoo! Mail  Tired of Vi@gr@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html

View raw message