Agent inherit -Xmx flag from application

If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text :slight_smile:

Kibana version: 7.5

Elasticsearch version: 7.5

APM Server version: 7.5

APM Agent language and version: 1.8 en

Browser version:

Original install method (e.g. download page, yum, deb, from source, etc.) and version: executable

Fresh install or upgraded from other version? Fresh install

Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.


Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

I use -javaagent flag to attach elastic-apm-agent to my java process with command:

start C:\ProgramData\Oracle\Java\javapath\java.exe -javaagent:C:\Tools\apm\elastic-apm-agent-1.8.0.jar -Delastic.apm.environment=xxx -Delastic.apm.service_name=xxx -Delastic.apm.server_url=xxx -Xmx512m -Delastic.apm.secret_token=xxx -jar xxx.jar

the problem is elastic-apm-agent inherit -Xmx flag from the application, is there a way to set -Xmx different for elastic-apm-agent? E.g. -javaagent::-Xmx256m

Steps to reproduce:

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Hi and thanks for your question.

The agent runs within the same JVM as your application, not in separate one, thus it shares the same heap configuration with your application.


Thanks for reply.


This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.