The database connection hangs due to a concurrent execution on the same database connection by:
- a database pool sweeper thread
- a thread handling regular transactions

If this occurs when cache loading, it can cause an incomplete cache to be built (for example, TableDescriptor). This can surface as various symptoms:

- Banner text shows as the word "null" (invalid table name: sys_script)
- System uses UI15 for all users when they expect UI16 (invalid table name "sys_user_preference")
- Node unreachable, blank page, 401's etc. (invalid field name "sys_scope.scope")
- Fields display as the field name instead of field labels (invalid table name: sys_documentation)
- Integrations receiving HTTP 401 (invalid table name: sys_user)
- Users unexpectedly logged out after logging in (invalid table name: sys_user)

These issues are always preceded by a series of SEVERE errors during the GlideSweep on threads that are being "cleaned." The errors are preceded by a warning message similar to the following:

com.glide.db.pool.DBPoolSweeperJobStatus@15cd039 WARNING *** WARNING *** caught error involing method getWarnings on connection 4

Steps to Reproduce

No steps to reproduce available at this time.


No workaround exists - client should upgrade to version with fix as soon as possible

Related Problem: PRB711226

Seen In

Eureka Patch 13 Hot Fix 5
Fuji Patch 12 Hot Fix 1
Fuji Patch 13 Hot Fix 1
Helsinki Patch 1
Helsinki Patch 2
Helsinki Patch 2 Hot Fix 2
Helsinki Patch 3
Helsinki Patch 3 Hot Fix 7
Helsinki Patch 4
Helsinki Patch 5

Fixed In

Helsinki Patch 2 Hot Fix 4
Helsinki Patch 3 Hot Fix 6
Helsinki Patch 6

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-08-14 14:01:31