BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
R_Chung
Quartz | Level 8

Hi, all.

 

I am encountering a problem that the environment manager always give out an alert message (HQ Agent Memory - JVM Free Memory < 14.3 MB (actual value = 10.6 MB))

 

I know what it is meaning and I would like to know how to tackle it so that it won't appear anymore.

 

1. I dont't want to edit/increase 14.3 in the definition part.

2. I have edited "SAS-configuration-directory/Levn/Web/WebAppServer/SASServer1_n/bin/setenv.sh" with new parameters : Xmx8192m -Xss256k -Xmso256k -Xms4096m -XX:PermSize:512m -XX:MaxPermSize:512m, but it seems no different.

 

Thanks for any help

1 ACCEPTED SOLUTION

Accepted Solutions
R_Chung
Quartz | Level 8

It is the correct file, but only changing the "wrapper.java.additional.2=-Xmx128m" cannot deal with the problem properly.

 

Also, you need to edit the "Initial Java Heap Size" which is initially commented and and the "Maximun Java Heap Size" too.\

 

For my setting, I have changed:

1. wrapper.java.additional.2=-Xmx1024m

2. wrapper.java.initmemory=512

3. wrapper.java.maxmemory=1024

View solution in original post

3 REPLIES 3
Technolero
Pyrite | Level 9

You said the message was for: (HQ Agent Memory - JVM Free Memory < 14.3 MB).

 

You changed the setting for SASServer 1, which doesn't help the agent.

 

1. Stop the agent (Even if it is not running just to be sure)

----------------------------

cd /<SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.0.0-EE/bin

./hq-agent.sh stop

 

2. Edit wrapper.conf

----------------------------

cd /<SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.0.0-EE/bundles/agent-5.0.0/conf

Edit wrapper.conf:

Look at entry  "wrapper.java.additional.2="

Default is "wrapper.java.additional.2=-Xmx128m"

Test with  -Xmx512m,

 

 

 

3. Restart agent:

----------------------------

cd /<SASCONFIG>/Lev1/Web/SASEnvironmentManager/agent-5.0.0-EE/bin

./hq-agent.sh start

R_Chung
Quartz | Level 8

It is the correct file, but only changing the "wrapper.java.additional.2=-Xmx128m" cannot deal with the problem properly.

 

Also, you need to edit the "Initial Java Heap Size" which is initially commented and and the "Maximun Java Heap Size" too.\

 

For my setting, I have changed:

1. wrapper.java.additional.2=-Xmx1024m

2. wrapper.java.initmemory=512

3. wrapper.java.maxmemory=1024

Technolero
Pyrite | Level 9

@R_Chung - Thanks for correcting me. I looked at my wrapper.conf file and noticed that I also had changed:

 

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=512

 

and received no more alerts.

 

 

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 1994 views
  • 9 likes
  • 2 in conversation