Article - CS360787
"APPARENT DEADLOCK!!!" is seen in the ApplicationLog.log and ThingWorx Platform becoems unresponsive after starting a connected Azure IoT Hub
Modified: 31-Jan-2023
Applies To
- ThingWorx Platform 8.4 to 9.3
- ThingWorx Connection Server 8.5 to 9.1.0
- Azure IoT Hub Connector
Description
- Connected Azure IoT Hub to ThingWorx Platform and ThingWorx becomes inaccessible
- APPARENT DEADLOCK!!! is seen in ThingWorx Platform ApplicationLog after starting the Azure IoT Hub
- Azure IoT Hub is causing ThingWorx Platform outages
- Started an Azure IoT Hub which is connected to ThingWorx Platform via the Azure IoT Hub Connector and the instance becomes inaccessible
- What are optimal settings for EventProcessingSubsystem Configuration when the Azure IoT Hub Connector is leading to many database executions
- Events fired by the Azure IoT Hub are making the ThingWorx Platform inaccessible
- After starting the Azure IoT Hub ThingWorx Platform ApplicationLog.log located in <ThingworxStorage>\logs\ shows messages similar to the following:
- [L: WARN] [O: c.m.v.a.ThreadPoolAsynchronousRunner] [I: ] [U: ] [S: ] [T: C3P0PooledConnectionPoolManager[identityToken->2zqamyal1rixscga4bik8|1d35c52a]-AdminTaskTimer] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@5238e7c7 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!'
This is a printer-friendly version of Article 360787 and may be out of date. For the latest version click CS360787