IDP V3: LockTimeoutException with remote PG DB

[Cantor, Scott]

On 10/8/15, 9:27 AM, "users on behalf of Marvin Addison" <users-bounces at shibboleth.net on behalf of marvin.addison at gmail.com> wrote:

>Your comment about the problem not showing up when the DB is local is puzzling. Perhaps there's some subtle but very bad behavior when application locks are held marginally longer, which I would expect would be the case for connections to a remote host.

At least with regard to the use of the database for persistent ID storage, and not sessions, I did discover that the default query timeout on that storage plugin was 0 (infinite).

We clearly still have code with inappropriate timeout defaults, so we have more work to do on that front, but I'm fixing that particular bug in the broader rewrite of that plugin to address the race conditions.

But obviously, using a timeout simply moves the problem to an error generating a stored ID. Ultimately the fault is with the network or database.

-- Scott