IDP V3: LockTimeoutException with remote PG DB

[Cantor, Scott]

On 9/30/15, 5:47 AM, "users on behalf of TISSOT Jacques" <users-bounces at shibboleth.net on behalf of jacques.tissot at unifr.ch> wrote:



>The following observation appears only when IDP is asking PG DB server remotely. I tried different (in global.xml) maxActive and maxIdle jdbc connectors (up to 32) without solving the problem. The problem does not appear when IDP is asking PG DB locally.
>
>I thought first it will be caused by the replication. But, it happens the same way if DB is not replicated.

I don't see what pool size has to do with it, unless you actually change the wait time.


Your database connection is hanging, or at least taking too long. Changing the timeouts (if the driver honors them) or fixing the database connectivity is the only way to fix the problem. You can't leave requests hanging indefinitely anymore, they'll tie up the system.

I haven't figured out exactly what the scope of the Spring lock is yet, but it appears to be held in ways that I wouldn't expect naively.

-- Scott