Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Java Runtime versions for LEM Agents

Java Runtime versions for LEM Agents

Table of contents
Created by James Nielsen, last modified by Abdul.Aziz on Jul 20, 2018

Views: 1,491 Votes: 0 Revisions: 16

Updated: July 20, 2018


This article provides information about the corresponding Java Runtime versions for LEM Agents for both windows and *nix operating systems.


  • LEM Agent 6.2 and later
  • All Windows and Linux versions


  • As of now, Solarwinds LEM agents install is only supported with OracleJDK officially. So, make sure you have OracleJDK 1.7 and higher installed on your Windows or Linux agent nodes.
  • LEM agent has not been tested with OpenJDK, hence not officially supported. However, we have seen many customers have LEM agents installed and working with OpenJDK as well.


The JRE version is fixed per LEM Agent version and requires an agent upgrade to change. 

  • LEM Agent version 6.2.0 and 6.2.1 use JRE 1.7.0_80.
  • LEM Agent version 6.3.1 uses JRE 8u92.


During a LEM agent upgrade, it is possible to tie the agent to a local JRE installation. This can be done by changing the appropriate JRE entry in the SWLEMAgent.lax file of the agent (located in the agent install directory):

  1. Back up the SWLEMAgent.lax file.
  2. Stop the LEM agent service.
  3. Open the file in a text editor and edit it to point to the required JRE:

If required, it is possible to delete the JRE version directories in the ContegoSPOP directory. 


Note: When the agent updates the SWLEMAgent.lax file, changes may be reverted back to the agent's own JRE install. 



Last modified



Internal Use Only