Shibboleth IdP freezing issue

[Cantor, Scott]

The first error has nothing to do with anything freezing or with any database, that's just back button. Trigger it yourself.

The second is probably related, and I wouldn't know anything about making a databse work. There's a reason the default is client side storage.

Other than "stop trying to use a database", or maybe twiddling with the retryable error settings to get it to retry transactions, no idea. If it's hung, then it's not going to help to be retrying errors, that will just cause more backlog.

The reason you don't see any deadlocks is that the error message is not true. Databases don't actually take locks anymore, they just detect dirty operations and then claim a "deadlock" when that isn't at all what a deadlock is. When a DBA, who does know, assumes the error isn't nonsense, they go looking for actual deadlocked connections in the database and none are there. That isn't really what's going on, it's just the database not honoring the isolation level properly.

But as to why it's hung, that would tend to mean a bad driver.

-- Scott