Notifications

46 views

Symptoms


MID server creating GBs worth of logs on host machine.

\agent\hs_err_pid22292.log 
\agent\replay_pid22292.log 

Cause


There is insufficient memory for the Java Runtime Environment.

As a result, these error report files are saved on agent folder

M:\ServiceNow\Prod\agent\replay_pid7904.log 

M:\ServiceNow\Prod\agent\replay_pid22292.log  

Errors: 
========= 
2018/11/13 16:00:43 | # There is insufficient memory for the Java Runtime Environment to continue. 
2018/11/13 16:00:43 | # Native memory allocation (malloc) failed to allocate 1459600 bytes for Chunk::new 
2018/11/13 16:00:43 | # An error report file with more information is saved as: 
2018/11/13 16:00:43 | # M:\ServiceNow\Prod\agent\hs_err_pid7904.log 
2018/11/13 16:00:43 | # 
2018/11/13 16:00:43 | # Compiler replay data is saved as: 
2018/11/13 16:00:43 | # M:\ServiceNow\Prod\agent\replay_pid7904.log 
2018/11/13 16:00:43 | JVM exited unexpectedly. 
2018/11/13 16:12:12 | # There is insufficient memory for the Java Runtime Environment to continue. 
2018/11/13 16:12:12 | # Native memory allocation (malloc) failed to allocate 131088 bytes for Chunk::new 
2018/11/13 16:12:12 | # An error report file with more information is saved as: 
2018/11/13 16:12:12 | # M:\ServiceNow\Prod\agent\hs_err_pid22292.log 
2018/11/13 16:12:12 | # 
2018/11/13 16:12:12 | # Compiler replay data is saved as: 
2018/11/13 16:12:12 | # M:\ServiceNow\Prod\agent\replay_pid22292.log 
2018/11/13 16:12:12 | JVM exited unexpectedly. 

Resolution


1. Open the \ServiceNow\<MID Server name>\agent\conf\wrapper-override.conf file in a text editor.

       For more information about this file, see Installing Multiple MID Servers on a Single System
 
2. Locate the following lines in the file:
      # OPTIONAL: Maximum Java Heap Size (in MB)
      wrapper.java.maxmemory=1024

3. Edit the memory allocation.

4. Remove the comment tag (#) from the memory allocation parameter.

5. Save the file.

6. Restart the MID Server service.

https://docs.servicenow.com/bundle/london-servicenow-platform/page/product/mid-server/task/t_MIDServerOptionalConfiguration.html

Article Information

Last Updated:2019-03-14 03:52:24
Published:2019-03-13