jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From qcfireball <qcfireb...@yahoo.com>
Subject Re: Sharing a Session or a Session per web user
Date Mon, 26 Nov 2007 18:38:02 GMT

Running a test of a thousand iterations, creating and maintaining a reference
to 1 Session per iteration, I found that a Session incurs approximately a
864 byte load.  Very very small, definately an insignificant load.  Creating
many Session Objects will not be a problem.



Alexandru Popescu ☀ wrote:
> 
> On Nov 26, 2007 4:27 PM, qcfireball <qcfireball@yahoo.com> wrote:
>>
>> I did a small test - 2 Threads each retrieving a property from different
>> Nodes 100 times each.
>> This executed without Exception.  I may try a more elaborate test than
>> this.
>>
>> Question:  what is the maximum number of concurrent read-only uses of a
>> Session would you recommend?
>> 10 / 50 / 100 / no limit?
>>
> 
> I don't think anyone can tell you this. It depends on a lot of
> specific details. You can start looking at the implementation and
> figure out the data structures used. Then you can search for various
> performance tests of those. Still, in the end it will be up to your VM
> and OS how good or bad those will behave.
> 
> ./alex
> --
> .w( the_mindstorm )p.
> 
>>
>>
>> Alexandru Popescu ☀ wrote:
>> >
>> > Paco, as you probably know by now, jcr Sessions are not thread safe,
>> > and so exposing them in a multi-thread environment may become a risk
>> > for the data. I am not sure how your application is behaving and how
>> > do you protect against thread contention at the session level, so it
>> > is kind of hard to give an advise. What I can share is the fact that
>> > in a read-only mode you can probably share a session between different
>> > threads.
>> >
>> > ./alex
>> > --
>> > .w( the_mindstorm )p.
>> >
>> >
>> > On Nov 21, 2007 6:15 PM, Paco Avila <pavila@git.es> wrote:
>> >> Hi
>> >>
>> >> Our application using Jackrabbit is an Document Management System
>> >> (OpenKM). Actually we prevent an user log into the web aplication
>> twice,
>> >> so there is only one Jackrabbit Session per web user.
>> >>
>> >> But we also expose several methods via WebServices and here is the
>> >> problem: if an user is logged into the web application, the same user
>> >> can't user WebService API because he is already logged into the
>> system.
>> >>
>> >> I have think two options:
>> >>
>> >>  - Reuse an existing Jackrabbit Session for both web user and the same
>> >> ws api user. PROBLEM: is it a good practice for Jackrabbit?
>> >>
>> >>  - The web user hace one JR Session and the ws api user have another
>> >> session. PROBLEM: Every web user need another WS user and this can be
>> >> hard to manage because we need to set permissions for both users and
>> >> should be the same permissions for them.
>> >>
>> >> Any tip?
>> >>
>> >>
>> >> --
>> >> GIT CONSULTORS
>> >>
>> >> www.git.es
>> >>
>> >> Tel: +34 971 498 310
>> >> Fax: +34 971 496 189
>> >>
>> >> C/ Francesc Rover, 2B.
>> >> 07003 Palma de Mallorca – Illes Balears (España)
>> >>
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Sharing-a-Session-or-a-Session-per-web-user-tf4851166.html#a13950210
>> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/Sharing-a-Session-or-a-Session-per-web-user-tf4851166.html#a13954710
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.


Mime
View raw message