article Using -server option to optimize Java memory usage

Setting the -server Java option will enable the up.time core to use the server JVM, which has enhanced performance and stability for applications that stay running for long periods of time (such as up.time).  To enable the -server option, complete the following steps for the appropriate Operating System:


NOTE: up.time 7.1 and later has this configured automatically so you will not need to apply it.  If missing from the configuration then contact uptime Support to review.

 

Unix Systems

  • Stop the up.time core: # /etc/init.d/uptime_core stop
  • Edit the /uptime.lax file and change the following line:
    • From: lax.nl.java.option.additional=-Djava.library.path=/usr/local/uptime/bin
    • To: lax.nl.java.option.additional=-server -Djava.library.path=/usr/local/uptime/bin
  • Start the up.time core: # /etc/init.d/uptime_core start

Windows Systems

  • Contact uptime Support to request the appropriate JVM version for your up.time release (see below).
  • Stop the up.time Data Collector.
  • Extract the JVM zip file into the \jre\bin directory within a server folder so it looks similar to: \jre\bin\server\jvm.dll.
  • Edit the \wrapper.conf file and add the sample line below to the end of the section labelled: Java Additional Parameters.
  • Note that X in the sample needs to be changed to be 1 more then the current parameter count. (For example if there's no additional parameters then the value should be 1, or if there's already 2 additional parameters then it should be 3)
    • Sample line: wrapper.java.additional.X=-server
  • Start the up.time Data Collector.

JVM -server Version Guidelines

  • up.time 5.0 requires jvm-server-1.5.0_10.zip
  • up.time 5.1 & 5.2 require jvm-server-1.6.0_11.zip
  • up.time 5.3, 5.4 & 5.5 require jvm-server-1.6.0_20.zip
  • up.time 6.0 require jvm-server-1.6.0_26.zip
  • up.time 7.0 require jvm-server-1.6.0_31.zip

Related Articles


Adjusting the Java Heap Size

RatingViews
article

By: uptime Support | Date Created: 2-16-2006 | Last Modified: 8-5-2013 | Index: 056

  22804

Java heap space Throwable: java.lang.OutOfMemoryError

RatingViews
article

Example error message: 2010-07-09 16:42:41,654 ERROR (PerfERDC:137) - service Platform Performance Gatherer (192) on host DKLBMMDB1 (34) Error getting data from agent: Java heap space Throwable:...

By: uptime Support | Date Created: 8-26-2010 | Last Modified: 8-10-2011 | Index: 495

  3454

Memory Consumption by Performance Counters

RatingViews
article

By: uptime Support | Date Created: 10-25-2005 | Last Modified: 7-12-2011 | Index: 041

  9412

IOException: Not enough space (Java heap)

RatingViews
article

This article explains the IOException: Not enough space message and how to resolve it.

By: uptime Support | Date Created: 1-12-2007 | Last Modified: 7-6-2011 | Index: 115

  4819

High CPU Usage on Windows Agent

RatingViews
article

If you observe high CPU usage on systems running the Windows agent, try disabling unused counters (e.g. IIS, SQL, Exchange, etc.) and then restart the agent. If this does not resolve the issue,...

By: uptime Support | Date Created: 7-12-2011 | Last Modified: 8-11-2011 | Index: 542

  3004

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement