Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Table of Contents |
---|
Problem
Some JVM implementations try to allocate the memory.max value at start-up time. If your machine could not allocate that amount of free memory, the JVM will not start and therefore the Kiuwan analysis will fail.
In this case, you will be presented with the same
...
Image Removed
...
error message as in Out of Memory.
Image Added
Click Analyzer log to open a window where the log file (temp/agentGUI.log) is displayed
...
. Here you will see the following error message
...
:
...
Image Added
You will find some lines as the following indicating that a JVM has exited with error 1.
Code Block |
---|
ERROR 2016-10-03 17:59:52,820 - ERROR running target "run.rules" - Java returned: 1 |
...
C:\Luis\Kiuwan\Nuevo\KiuwanLocalAnalyzer\bin\analyzerCommon.xml:79: Java returned: 1 |
Most of the
...
time, this indicates that the operating system is not able to allocate the configured memory to the JVM process.
If you are using Kiuwan Local Analyzer in CLI mode, this error is reported to the standard output.
...
Image Added
Solution
Panel |
---|
...
bgColor | #fff |
---|
To solve it, |
...
|
...
|
...
If your problem persists, please contact Kiuwan Technical Support.
|
...
|
Related articles
Content by Label | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
|
Page properties | ||
---|---|---|
| ||
|
...