Problem
Kiuwan Local Analyzer incorporates a safety mechanism that avoids concurrency problems when automatically upgrades.
This mechanism avoids two conflicting scenarios:
- To upgrade when analysis are running
- To analyze when upgrading is running
To implement this mechanism Kiuwan Local Analyzer create some *.lock files that under normal conditions control this synchronization.
Nevertheless, under some special circumstances (JVM crashes, user kills JVM, etc) it might be possible that those *.lock files remain.
If this happen, following situations may occur:
- Analyses halt and do not progress (get blocked)
- Automatic upgrade does not finish (get blocked and time out)
Solution
Remove all *.lock files that might exist under your Kiuwan Local Analyzer installation.
This removal can be done executing next command:
agent.cmd --clean
Additionally, there is configuration property in conf/agent.properties that affects this behaviour:
# Max time (in seconds) to wait for running analysis to end before upgrading agent
analysis.timeout=3600
This is the max time (1 hour by default) a new analysis will wait for running analysis to end before upgrading agent. You can reduce this value in case you consider your local analyses should end in less than 1 hour.
Related articles