Shibboleth Developers

[giacomo tenaglia <>]

On Thu, Feb 14, 2008 at 11:24:54AM -0500, Scott Cantor wrote:
> > I'm testing ODBC store on Oracle with a load of 250 new sessions per
> > day, with two machines.
> 
> That's obviously not a load, it would qualify as trivial usage. My point
> being I don't think this tells us a lot. If anything it says even no load
> has some issues.

Yes, it was not meant to be "heavy load", but it's more than my previous
tests on my local machine.

> > Everything seems to work fine (I'm having some "replay detected of
> > message ID", but I don't think they're critical), and this is very good
> > since we need to use Shibboleth authentication on a lot of load balanced
> > servers.
> 
> Replay usually just means the user got back button happy. IdPs SHOULD
> prevent this. It frustrates me that more don't.

It's ADFS, so this is not the main frustrating issue..

> Basically, I'm ok with exposing a property to set the isolation level. But
> I'm not ok with setting it to READ_COMMITTED (which is not ACID, it's the
> second lowest iso level) for everybody. And I don't know what the
> implications would be in all cases.
> 
> My preference is to do some research into detecting lock contention so I can
> just retry the transaction.

Ok, I will see if I can find something that can help. The only problem I
see is that maybe this is backend-related, so you will have to check for
the behaviour of every (supported) database.

giacomo

-- 
giacomo tenaglia
Technical Student at CERN IT/DES-SIS
CNR Biblioteca d'Area di Bologna - http://biblio.bo.cnr.it
Phone +41 76 5003376 - 
sip: