No flow execution could be found with key 'e1s1'

Cantor, Scott cantor.2 at osu.edu
Wed Aug 23 21:17:07 EDT 2017


On 8/23/17, 9:05 PM, "users on behalf of Y Levine" <users-bounces at shibboleth.net on behalf of ylevine20 at gmail.com> wrote:

> Are they linked? What could be the root cause?

They have nothing to do with each other. The root cause is that Oracle stopped supporting transactions and locking properly many years ago, as have many other databases, because of a misguided attempt to favor performance over correctness. The code assumes transactions and locking work because that's what the SQL standard says should happen. When the database doesn't honor that, the code breaks and retries a set amount and eventually gives up and fails whatever it was trying to do.

> We are using Stoiragerecords --- on an Oracle DB

I would reconsider using a database, and absolutely wouldn't use one for the IdP's sessions. I wouldn't use one for anything if it was in any way avoidable.

-- Scott




More information about the users mailing list