[support] 00008 - Failed to read lock file integer error

Author | Judith López

Version | 1.0

Updated | 19th Jan 2021

Categories | [support]

Applies To

All Windchill versions.

Description

• Errors appear in the MS log on startup

This is due to the lock file used to limit the initialization to a single server.

The other server if they cannot read the lock file or this file is corrupt by produce these error, however after a few minutes the system will recover and will remove the lock. This will delay slightly the startup of the server, only for wex services, but will not occur on a second restart

2020-03-04 18:55:56,254 INFO  [SessionThread-3] wt.system.err  - 2020-55-05 00:55:56 INFO  com.wincomplm.wex.kernel.impl.manager.WexKernelManager - Initializing Wex Kernel...
2020-03-04 18:55:56,440 INFO  [SessionThread-3] wt.system.err  - 2020-55-05 00:55:56 INFO  com.wincomplm.wex.kernel.impl.concurrent.WexFileLock - Trying to aquire the lock...
2020-03-04 18:55:56,441 INFO  [SessionThread-3] wt.system.err  - 2020-55-05 00:55:56 INFO  com.wincomplm.wex.kernel.impl.concurrent.WexFileLock - Could not acquire lock.
2020-03-04 18:55:56,441 INFO  [SessionThread-3] wt.system.err  - 2020-55-05 00:55:56 INFO  com.wincomplm.wex.kernel.impl.concurrent.WexFileLock - Waiting for the lock to be released...
2020-03-04 18:55:57,443 INFO  [SessionThread-3] wt.system.err  - 2020-55-05 00:55:57 INFO  com.wincomplm.wex.kernel.impl.concurrent.WexFileLock - Failed to read lock file integer
2020-03-04 18:55:58,444 INFO  [SessionThread-3] wt.system.err  - 2020-55-05 00:55:58 INFO      com.wincomplm.wex.kernel.impl.concurrent.WexFileLock - Failed to read lock file integer

Solution

This is corrected in Manager 1.12 that is included in Platform 1.4.