ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Proxy Client ends with error and coredump every few hours and must be restarted
Article ID: 84344
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
No Automic internal error message is written, but the core dump is named "cheap.bin" if it is created.
Proxy Client ends with error and core dump every few hours and must be restarted.
This occurs occasionally after a time period between a few hours and several days. Dependent on the available memory on the machine that the Proxy server process is running on it will crash with a dump file called "cheap.bin" which will be written to the bin directory.
After that a restart enables the proxy to run again.
Note: The error has been seen on SUN Solaris but could also occur on other Operating Systems.
No Automic internal error message is written, but the core dump is named "cheap.bin" if it is created.
Proxy Client ends with error and core dump every few hours and must be restarted.
This occurs occasionally after a time period between a few hours and several days. Dependent on the available memory on the machine that the Proxy server process is running on it will crash with a dump file called "cheap.bin" which will be written to the bin directory.
After that a restart enables the proxy to run again.
Note: The error has been seen on SUN Solaris but could also occur on other Operating Systems.
Cause
Cause type:
Configuration
Root Cause: Java Version 1.8.0 causing a memory leak
Configuration
Root Cause: Java Version 1.8.0 causing a memory leak
Environment
OS Version: N/A
Resolution
After Analysis this issue was found as a memory leak due to using Java version 1.8.0 and is causing the Proxy process to assign large amounts of memory to keep up with its work. Depending on the machine configuration and usage of the proxy it can take between a few hours to days before the proxy will fail.
The Memory leak causing the issue was found to be with Java version 1.8.0.
Using Java of the latest 1.8 solves the issue, and the proxy remains stable after the Java upgrade.
Fix Status: No Fix
Fix Version(s):
N/A
The Memory leak causing the issue was found to be with Java version 1.8.0.
Using Java of the latest 1.8 solves the issue, and the proxy remains stable after the Java upgrade.
Fix Status: No Fix
Fix Version(s):
N/A
Additional Information
Workaround :
Restart the Proxy Process manually if it fails.
Restart the Proxy Process manually if it fails.
Feedback
Yes
No
Powered by
