The original bug was closed as it was a matter of a configuration issue:
It was caused by missing memory limit set to Java.
JVM_MAX_MEM=4G where 4 can be replaced by another appropriate value fixes this bug and this fix explanation should be added to the doc as part of the requirements.
Bug description:
Description of problem:
Analysis of tackle-testapp is stuck when running on Linux Arm64, sometimes it causes VM to hang
Version-Release number of selected component (if applicable):
7.2.0-21
How reproducible:
100%
Steps to Reproduce:
1. Enable containerless mode
2. Run command
$ /home/ec2-user/bin/mta-cli analyze --overwrite --input /home/ec2-user/kantra-cli-tests/data/applications/tackle-testapp --output /home/ec2-user/reports/
Actual results:
Analysis gets stuck with the ouput
time="2024-11-14T10:29:59Z" level=info msg="\n running analysis in containerless mode" time="2024-11-14T10:29:59Z" level=info msg="running source analysis" time="2024-11-14T10:29:59Z" level=info msg="creating provider config" time="2024-11-14T10:29:59Z" level=info msg="setting provider from provider config" provider=java time="2024-11-14T10:29:59Z" level=info msg="setting provider from provider config" provider=builtin time="2024-11-14T10:29:59Z" level=info msg="parsing rules for analysis" rules=/home/ec2-user/.kantra/rulesets time="2024-11-14T10:30:01Z" level=info msg="starting provider" provider=builtin time="2024-11-14T10:30:01Z" level=info msg="starting provider" provider=java time="2024-11-14T10:30:27Z" level=info msg="running depencency analysis" time="2024-11-14T10:30:27Z" level=info msg="evaluating rules for violations. see analysis.log for more info"
See analysis.log attached
Expected results:
It should complete successfully.
Additional info: