Article - CS393654
One of ThingWorx cluster nodes fails to startup due to I/O error
Modified: 29-May-2023
Applies To
- ThingWorx Platform 9.0 to 9.4
Description
- One of ThingWorx cluster nodes fails to startup with error reports:
[L: ERROR] [O: c.t.p.ThingworxDefaultTransaction] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] Could not commit the transaction. Rolling back... [L: WARN] [O: c.m.v.c.i.NewPooledConnection] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] [c3p0] A PooledConnection that has already signalled a Connection error is still in use! [L: WARN] [O: c.m.v.c.i.NewPooledConnection] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] [c3p0] Another error has occurred [ org.postgresql.util.PSQLException: This connection has been closed. ] which will not be reported to listeners! [L: ERROR] [O: c.t.p.PersistenceProviderTransactionManager] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] Error occurred during commit for the ThingworxPersistenceProvider persistence provider. [L: ERROR] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] !!!!! Error loading model [L: WARN] [O: c.t.l.ZookeeperSemaphore] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] Attempt to release lock /locking/mutex/loadModelMutex, but no leases are currently held [L: ERROR] [O: c.t.s.ThingWorxBootstrapper] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] *** CRITICAL ERROR ON STARTUP: Unable to initialize and start system: An I/O error occurred while sending to the backend. [L: ERROR] [O: c.t.s.ThingWorxBootstrapper] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] *** Web Application STATE is being set to ERROR! *** [L: WARN] [O: c.t.l.ZookeeperSemaphore] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] Attempt to release lock /locking/semaphore/ThingWorxServerloadModelSemaphore, but no leases are currently held [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [P: twx3] [T: main] >>>>>>> PLATFORM SHUTDOWN START <<<<<<<<<
- The other cluster nodes work correctly
- The startup hangs for more than one hour to load huge model, then reports upper database I/O error
- Tomcat JVM consumption is not at high level, tomcat can startup correctly
- Issue is still observed after deleting /tomcat/webapps/Thingworx runtime folder
This is a printer-friendly version of Article 393654 and may be out of date. For the latest version click CS393654