Article - CS255556
Detecting Deadlocks / Blocked Statements in PostgreSQL for ThingWorx Platform
Modified: 15-Feb-2023
Applies To
- ThingWorx Platform 6.5 to 9.3
Description
- How to tell if there are blocked statements on a PostgreSQL database?
- Detecting database deadlocks on PostgreSQL
- <ThingworxStorage>\logs\ApplicationLog.log output the following message:
- [L: WARN] [O: c.m.v.a.ThreadPoolAsynchronousRunner] [I: ] [U: ] [S: ] [T: C3P0PooledConnectionPoolManager[identityToken->2zuldxag1kh7a7kbhogh4|1def0024]-AdminTaskTimer] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@6dbc51 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
This is a printer-friendly version of Article 255556 and may be out of date. For the latest version click CS255556