connectionLimit default inconsistency, problems with CFAdmin (action=updateDatasource)

Description

the default for the 'connectionLimit' datasource parameter is inconsistent between the UI (default='inf' or '-1) and CFAdmin(updateDatasource) (default=100)

Also, passing 'connectionLimit=-1' to CFAdmin(action='updateDatasource') isn't working - the value comes back as 100 (CFAdmin(action=getDatasource)).

If I set the connectionLimit value to 999 in the updateDatasource call, the value '999' is returned by getDataSource - and the UI shows 'inf' for the datasource

This should all be academic, but since we upgraded to 5.3.3.62 (from 5.3.2.77), we've been seeing the connection pool getting clogged up (to the point where timeout exceptions are thrown when trying to validate the datasource). In our testing scenario (where an instance has one user in the foreground and one or two database-heavy processes running in the background via CFSchedule), a limit of 100 should be more than adequate - but it's not... which points to a possible problem with connections not being correctly returned to the pool

Environment

CentOS7 VM, Java 11

Status

Assignee

Michael Offner

Reporter

Tim Parker

Labels

None

Affects versions

5.3.3.62

Priority

New
Configure